What is discovered?
The Maven 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 type||CAST Delivery Manager Tool interface||Resulting source package configuration|
|Maven project simplified support (versions 2 and 3)|
Configures a project on each folder that contains a pom.xml file except when the type of packaging declared in the pom.xml is "pom".
Click to enlarge
The following messages emitted by the discoverer may appear during the packaging action:
|Error||cast.dmt.discover.jee.maven.resources.pomAnalysisFailed||The analysis of POM file %PATH% has failed||Verify the corresponding file. If the file is good, please raise a ticket.|
|Warning||cast.dmt.discover.jee.maven.project.superPomParseError||Error parsing Maven Super POM!||Technical issue. Please contact Support.|
|Warning||cast.dmt.discover.jee.maven.project.parseError||Error parsing Maven project '%FILE_PATH%'||Verify the corresponding file. If the file is good, please raise a ticket.|
|Warning||cast.dmt.discover.jee.maven.noPackaging||No packaging found in maven file %PATH%||This project will be considered as a jar.|
|Warning||cast.dmt.discover.jee.maven.missingPomParent||The maven parent artifact %PARENT% required by the maven artifact %ID% is missing.||Make sure that the pom.xml file of the parent is included in the source code of this package.|
|Warning||cast.dmt.discover.jee.maven.resources.jarFileNotFound||The jar file is not present in the maven artifact folder %PROJECT_PATH%||The maven artifact is ignored to avoid to hide the alert. Please raise a ticket to investigate the issue.|
|Warning||cast.dmt.discover.jee.maven.moreWebService||More then one webservice file %FILE_PATH% discovered in project.||You can either ignore this warning and select the WSDL version manually in the Analysis Unit for that project or you need to reconfigure your project to a single WSDL file (web descriptor).|
When a pom.xml file defines a dependency as "optional", a "missing project" alerts will be raised for the dependencies, even if they are actually present. These missing project alerts can be ignored. For example, the following will raise a missing project alert for "junit":
When a dependency <version> is defined in a <properties> tag in the parent pom.xml, then the CAST Delivery Manager will be able to successfully locate the project. However, if the <properties> tag is then followed by a <profile> in a <profiles> tag, the CAST Delivery Manager is not able to recognize the dependent project and an undefined variable alert will be raised for this. To solve the undefined variable alert:
- reconfigure the pom.xml by removing the <profile>
- manually remediate the alert in the CAST Delivery Manager Tool