Page tree
Skip to end of metadata
Go to start of metadata


What is discovered?

The Eclipse Project Discoverer is not currently provided as an extension: instead it is embedded in CAST AIP Core and is therefore present "out of the box".

Supported project typeCAST Delivery Manager Tool interfaceResulting source package configuration
Eclipse project support (all versions greater than 3)

Configures a project for each Eclipse Java project (.project with Java nature) identified:

Click to enlarge

  • Application root path:
    • using WEB-INF/web.xml grand parent folder if it exists
  • Source folders configured in .classpath
  • Class path configured in .classpath
  • Java language & environment (1.1 to 8.0) according to .classpath and project settings
  • XML files found in project folder (excluding files in Eclipse .settings folders and output class folders)
  • PROPERTIES files found in project folder (excluding files in output class folders)
  • Libraries according to jar names in the project classpath: JUnit, Log4J, Commons logging, DOM4J, JSF, MX4J, Hibernate, Struts, Spring

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.

Note about 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.

  • No labels