commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Caswell" <ste...@caswell.name>
Subject RE: installing jakarta code Was: using commons components and logging
Date Fri, 08 Nov 2002 21:15:39 GMT

> -----Original Message-----
> From: Henri Yandell [mailto:bayard@generationjava.com] 
> Sent: Friday, November 08, 2002 3:55 PM
> To: Jakarta Commons Developers List
> Subject: Re: installing jakarta code Was: using commons 
> components and logging
> 
> 
> 
> 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?

Maven will generate the zips/tar.gz's, so others can still download the
full distribution. Having [lang] mavenized would not force other
projects to mavenize just to use the [lang] library.

> 
> 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.
> 

I believe Maven provides a great solution to this issue. The site that
Maven generates does contain a list of a project release's dependencies
(not that [lang] has any, but this is a nice standard place for a
project to publish it's dependency list). Personally I'd love to see all
of commons migrate toward Maven, for this very reason. It provides
standard documentation and a standard way to build projects.

And for a project like [lang], Maven is not all that revolutionary. I
Mavenized a similar commons-type project at my work with very little
effort. And the bang for the buck was incredible.

> 
> Hen
> 
> On Sat, 9 Nov 2002 dion@multitask.com.au wrote:
> 
> > Henri Yandell <bayard@generationjava.com> 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>
> 
> 

Steven Caswell
steven@caswell.name
a.k.a Mungo Knotwise of Michel Delving
"One ring to rule them all, one ring to find them..."



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message