[EMAIL PROTECTED] wrote:
These days, there is a version of jaxp in the JDK. So Ant should only depend on the JDK.
Bootstrapping maven is fairly lean. It just uses ant and jaxp. The bootstrap process does download the jars needed to compile and build maven though. How does ant get built? xml-commons produces JAXP, and there's a circular dependency between it and ant, right?
I don't want to verify that maven builds against the version of its dependencies that it choses to download, I want to verify that maven can be built against the version of the dependencies I have built. So, in other words, I want to employ the "jar override feature" that you describe below during the bootstrap process itself.
This is known as the jar override feature. If maven.jar.override is set to true, then maven looks for a property that tells it the location of that jar file. i.e. if maven.jar.override=true and maven is looking for 'ant', it gets the absolute location for the ant jar from the value of the property 'maven.jar.ant'. We'd need a mapping between gump's project id and maven's.
Though, it should be easy enough to get gump to set up properties for the various jars :)
Sounds doable.
3) there also is the issue of ordering maven builds. Between Maven and Gump, somebody would need to understand enough of maven's project descriptors to order the compilations of projects.
I figure between the two of us we should be able to do it.
+1 - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
