So you suggest that we no longer create zips/tar.gz's and just put jars on a Maven repository and tell everyone that to use a library they must build with Maven?
I think Maven could help with this, or a similar tool, but in a different way. When the tool creates our distribution, it also creates an ant file which contains the dependencies that are needed and can be run. ant -f get_dependencies.xml this sucks each dependency down [no project.xml remember, it's just a part of the tar.gz] and puts them in a directory called 'dependencies' or 'lib' or something. It can happily use the maven biblio, though that implies that a much faster build -> maven repo turn around is needed. What I'm looking for are ideas that will work with the existing structure and not revolutions :) So, how can we re-package our current code so that user's don't plough every-time into the dependency hunt. Hen On Sat, 9 Nov 2002 [EMAIL PROTECTED] wrote: > Henri Yandell <[EMAIL PROTECTED]> wrote on 08/11/2002 01:28:26 PM: > > > > > There has got to be a better way for us to handle installs and > > cross-dependencies, withing Commons and within Jakarta projects. It has > to > > be the number one problem that users have. > > Hence the development of Maven. > > > > > Hen > -- > dIon Gillard, Multitask Consulting > Work: http://www.multitask.com.au > Developers: http://adslgateway.multitask.com.au/developers > > > -- > To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
