On Tue, 25 Jun 2002, <[EMAIL PROTECTED]> wrote: > Can gump bootstrap maven using it's existing process (i.e. download > existing versions of jars) and then use that to build the > dependencies?
This could be a layered process similar to how Ant currently works: * bootstrap Maven with its built-in process * build all components that Maven depends upon using this bootstrapped Maven version (or - preferably? - plain Ant). * build Maven again using these components * use this second Maven version to build all other components that use Maven as their build tool. I think this would work, what we need for this: (1) A definition of how to use Maven to build something. Is it just invoking a Java class with a preconfigured CLASSPATH like using Ant? Is it invoking Ant on something? This could lead to a <maven> tag in Gump descriptors. (2) Some way to make sure that Maven built projects do not use the jar repository. Not using versioned jars is the whole point of Gump. Is this possible within Maven? One way would be to use the jardir attribute of the Gump workspace and make Maven use this directory as jar repository, although I think that Maven and Gump use different layouts here (Gump's is hierarchical with a directory per Gump project). If Maven provides a way to not use the lib repository and rely on CLASSPATH only, this would be the preferred option, though. The jardir attribute is optional for Gump right now and we'd have to make it required to use Maven. (3) Gump descriptors for all things that Maven depends upon. If we have (1), this doesn't require a vanilla Ant build file anymore. (4) Somebody to take care of Maven's dependency list and Gump descriptor. I'll be happy to help with the process and use my own Gump installation to testdrive it. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
