> Is a key feature of gump. Gump does not trust any project to set it's own classpath. it always completely handles the classpath. >
I think we all know we are 'holding our Gump nose somewhat' for the purpose of a first cut integration. We are feeling out this relationship. We can (w/ good will of each/the community) enrichen the relationship (via CVS HEAD) as the value of the relationship becomes recognized. (Consider this the Gump team meeting the Maven team a little past half way, and hoping for some reciporocity over time. ;-) I think we can show projects being semi-Gumped via Maven, we need a roadmap along the lines of the following to truely marry the two: 1) Parrallel a few existing Maven projects to use a project with <maven as well as using <ant, to test drive this with real data. 2) Work on the Maven 'gump' goal, to write the descriptor the new way (using <maven not <ant.) 3) Work together to ensure that artifact ids are consistent in both worlds. 4) Work to get the full Maven stack gumped (from scratch) each night, so we can use that instead of a packaged Maven. 5) Work to avoid maven.sh|maven.bat, and tap in to Maven w/ slightly more control at the JVM level. [E.g. JVM's awt.headless and such.] Along the way we need to look for subtleties, like have occured w/ Ant, over forked sub-VMs and the like. >From there, who knows ... Thoughts? regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
