...
| Format | Message ID | Message | Remediation |
|---|---|---|---|
| Error | cast.dmt.discover.eclipse.jee.createXMLReaderFailure | Internal error while creating an XML reader | Please contact Support. |
| Error | cast.dmt.discover.eclipse.jee.ioExceptionInClasspathParsing | Error 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. |
| Error | cast.dmt.discover.eclipse.jee.saxExceptionInClasspath | Error 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. |
| Error | cast.dmt.discover.eclipse.jee.createXMLReaderFailure | Internal error while creating an XML reader | Please contact Support. |
| Error | cast.dmt.discover.eclipse.jee.ioExceptionInClasspathParsing | Error 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. |
| Error | cast.dmt.discover.eclipse.jee.saxExceptionInClasspath | Error 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. |
| Warning | cast.dmt.discover.eclipse.jee.userDefinedJREContainerNotSupported | User 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. |
| Warning | cast.dmt.discover.eclipse.jee.unsupportedJVMType | The 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. |
| Warning | cast.dmt.discover.eclipse.jee.unsupportedClassPathEntryKind | Classpath 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 |
| Warning | cast.dmt.discover.eclipse.jee.readSettingsFileFailure | Error 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. |
| Warning | cast.dmt.discover.eclipse.jee.noSourceLevelInfoInSettingsFile | No 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. |
| Warning | cast.dmt.discover.eclipse.jee.project.multipleWebInfWebXmlFound | Multiple 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. |
| Warning | cast.dmt.discover.eclipse.jee.project.manifestFileNotFound | META-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 in the CAST Delivery Manager Tool, 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 packaging action.
See also How do I fine-tune my Version for more information.