Component validation

[starksm64]

Related to http://jira.jboss.com/jira/browse/JBBUILD-248, we need more validation on a component definition. A proper version, license type, project page, and description are a minimum set of attributes a component must declared to be usable by another project. A component without this info such as the current http://repository.jboss.com/junitejb/1.4/component-info.xml

<project name="junitejb-component-info">
 <component id="junitejb"
 version="1.4"
 >
 <artifact id="junitejb.jar"/>
 <export>
 <include input="junitejb.jar"/>
 </export>

 </component>

</project>

should cause any build which attempts to import this component to fail. Does maven support this level of validation?

[ryan.campbell]

It sounds like this is possible in Maven since you can recursively iterate over each dependency set and then make assertions about their POM. What do you think, Ruel?

[starksm64]

The current http://repository.jboss.com/maven2/ example is not compatibile with these requirements as there is no project page, no license info, and no description in the poms:

http://repository.jboss.com/maven2/apache-avalon-logkit/logkit/1.2/apache-avalon-logkit-1.2.pom

<project>
 <modelVersion>4.0.0</modelVersion>
 <groupId>apache-avalon-logkit</groupId>
 <artifactId>logkit</artifactId>
 <version>1.2</version>
</project>

The required elements are there based on the schema:
http://maven.apache.org/maven-v4_0_0.xsd

[ruel.loehr]

Ryan is correct. I setup an initial custom plugin to handle these assertations this afternoon, and the proof of concept works. I'll clean this up and commit it into the prototype as well as fixing the existing poms.

The same functionality can be extended to cover the generation of a license-info.xml (as each dependency pom can contain license info). I will set this up as well.