I have made progress. I have a patch for the
maven-remote-resources-plugin which allows one to add <supplement>
elements to the maven-remote-resources-plugin in your POM:
<artifactId>maven-remote-resources-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>process</goal>
</goals>
<configuration>
<supplements>
<supplement>
<![CDATA[
<project>
<groupId>xerces</groupId>
<artifactId>xmlParserAPIs</artifactId>
<name>Apache Xerces</name>
<url>http://xerces.apache.org/</url>
<organization>
<name>Apache Software Foundation</name>
<url>http://www.apache.org/</url>
</organization>
</project>
]]>
</supplement>
... more <supplement> elements ...
Anything included in the <supplement> is merged with the existing model
for the artifact. Right now <groupId> and <artifactId> are required
elements.
The CDATA is kind of ugly but I don't know how/have time to make it
better. I plan to add support for packaging the supplements up in a jar
file instead of polluting the pom with hundreds of lines of XML.
I'll put the plugin in Pluto under a Pluto groupId, extending the
maven-remote-resources plugin, so we can move forward with a release
(maven release plugin wouldn't allow us to release with a dependency on
a snapshot version of maven-remote-resources). I'll submit a patch to
the Maven group, and hopefully it will get accepted for the next release
of the maven-remote-resources plugin.
Hopefully I'll have this banged out by tomorrow eve.
Elliot
David H. DeWolf wrote:
I'd say we do that and also add download urls for all of them so they
appear like xml-apis.
<snip>
