On Thu, 27 Nov 2003, Brett Porter <[EMAIL PROTECTED]> wrote: >> Historically it has been phase 1 and even succeeded at one >> point. Currently Gump's inability to build dom4j or jaxen is >> probably the biggest problem for getting Maven built. > > I must have missed something... So gump can't use any JARs it > doesn't build itself?
Uhm, no. But in order to follow Gump main goal - be an early indicator for backwards incompatible changes - it wants to. Current CVS HEAD of dom4j doesn't compile against any released version of jaxen - and current CVS HEAD of jaxen doesn't compile against the latest JDOM. So, in order to build a project that depends on jaxen or dom4j, those projects have to depend on "packaged" versions of either. packaged means that it is some installed jar of a released version. "packaged" jaxen and dom4j jars are available but not heavily used ATM. > One issue will be the plugins... We have slated some work for 1.1 to > clear up how different versions will interact, but at the moment > certain projects may need a variety of plugin versions. In the spirit of Gump all those projects would always see the very latest version of each plugin. Again, to detect backwards incompatible changes (or to push the depending project to stop using deprecated stuff, of course). The alternative would be to have separate Gump packages for those different versions and make the projects each depend on a specific package. > SNAPSHOT is sort of the identifier for "latest build". So if gump > were building snapshots, Maven could use them. It does (and does so for non-Maven projects), see <http://gump.covalent.net/jars/latest/>. It may not follow a directory layout usable by Maven, though. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
