Extension ID

com.castsoftware.dmtjeeeclipsediscoverer

What's new ?

See Eclipse Project Discoverer - 1.0 - Release Notes for more information.

Extension description

This discoverer detects a project for each Eclipse Java project (.project) identified.

In what situation should you install this extension?

This extension should be used when you are analyzing Eclipse based JEE applications. The discoverer will automatically detect one project for every Eclipse Java .project file configured as follows:

One corresponding Analysis Unit (per project) will then be created for analysis purposes.

  • project inheritance and project aggregation is supported
  • the pom.xml must be valid XML and not contain any erroneous characters or spaces - you can check the consistency of an XML file by opening it in a browser - errors will be shown.

Resulting source package configuration

Technical information

The discoverer is already embedded in AIP Core. This embedded version of the extension will not undergo any further updates and instead all functional changes/customer bug fixes will be actioned in the extension.

Eclipse support

Eclipse project support

Supported

≥ 3.x(tick)

AIP Core compatibility

This extension is compatible with:

AIP Core release

Supported

8.3.x(tick)

Download and installation instructions

This extension will not be automatically installed when Eclipse related .project files are delivered - the embedded discoverer will be used. Instead if it is required, the extension should be downloaded and installed "manually":

Packaging messages

The following messages emitted by the discoverer may appear during the packaging action:

FormatMessage IDMessageRemediation
Errorcast.dmt.discover.eclipse.jee.createXMLReaderFailureInternal error while creating an XML readerPlease contact Support.
Errorcast.dmt.discover.eclipse.jee.ioExceptionInClasspathParsingError during .classpath file parsing. The format may not be supported, the file may be corrupted or it may not be an eclipse at all. The project is ignored: %PROJECT_PATH%Please contact Support.
Errorcast.dmt.discover.eclipse.jee.saxExceptionInClasspathError during .classpath file parsing. The format may not be supported, the file may be corrupted or it may not be an eclipse at all. The project is ignored: %PROJECT_PATH%Please contact Support.
Errorcast.dmt.discover.eclipse.jee.createXMLReaderFailureInternal error while creating an XML readerPlease contact Support.
Errorcast.dmt.discover.eclipse.jee.ioExceptionInClasspathParsingError during .classpath file parsing. The format may not be supported, the file may be corrupted or it may not be an eclipse at all. The project is ignored: %PROJECT_PATH%Please contact Support.
Errorcast.dmt.discover.eclipse.jee.saxExceptionInClasspathError during .classpath file parsing. The format may not be supported, the file may be corrupted or it may not be an eclipse at all. The project is ignored: %PROJECT_PATH%Please contact Support.
Warningcast.dmt.discover.eclipse.jee.userDefinedJREContainerNotSupportedUser defined JRE (%PATH%) are not supported. This information will not be used for the project: %PROJECT_PATH%Nothing to do in the delivery. Before running the analysis in CMS, you must define the value for the corresponding Analysis Unit or define a default value for the application.
Warningcast.dmt.discover.eclipse.jee.unsupportedJVMTypeThe JVM name "%NAME%" is unknown or not supported. This information is ignored for the project: %PROJECT_PATH%Nothing to do in the delivery. Before running the analysis in CMS, you must define the value for the corresponding Analysis Unit or define a default value for the application.
Warningcast.dmt.discover.eclipse.jee.unsupportedClassPathEntryKindClasspath file entry kind "%KIND%" with path "%PATH%" is not supported. This information is ignored for the project: %PROJECT_PATH%Nothing to do in the delivery. Before running the analysis in CMS, you must define the value for the corresponding Analysis Unit or define a default value for the application. This message is expected.
Warningcast.dmt.discover.eclipse.jee.readSettingsFileFailureError during reading of eclipse settings file. The content is ignored for the project: %PROJECT_PATH%Check the content of this file. Before running the analysis in CMS, you must define the java version for the corresponding Analysis Unit or define a default value for the application.
Warningcast.dmt.discover.eclipse.jee.noSourceLevelInfoInSettingsFileNo source level information in eclipse settings file. Maybe the file is corrupted: %PROJECT_PATH%Before running the analysis in CMS, you must define the java version for the corresponding Analysis Unit or define a default value for the application.
Warningcast.dmt.discover.eclipse.jee.project.multipleWebInfWebXmlFoundMultiple web application descriptor files has been found. Only the first one will be used in the project configuration: %PROJECT_PATH%Check the folder structure under this project. You might have duplicated code.
Warningcast.dmt.discover.eclipse.jee.project.manifestFileNotFoundMETA-INF/MANIFEST.MF is required but was not found at the expected location: %PROJECT_PATH%.The eclipse project is based on OSGi. Check why the file is not provided.

Notes

Missing source folder alerts

When packaging Eclipse based Java code, you may receive Missing source folder alerts even though the source folder that is recorded as being missing is actually present in the source code. This alert is usually generated when no .project file has been found in the folder that is recorded as being missing. To resolve this alert, you can manually add the missing .project file and then re-run the source code delivery.