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?
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:
<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:
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.