> On Wed, 2002-07-10 at 09:50, James Strachan wrote:
> > Just a thought; I'm just about to hack the jelly build so that the
binary
> > distro comes with a lib directory containing all the jars it depends on.
>
> How about a target that brings them down if the user wishes? Somehow
> utilize the local repository to promote reuse. I suppose some might want
> full containment for the distros, but if we could manage to somehow
> provide instructions in the dist that could pull down the resources
> without having maven installed than I would prefer that. Maybe something
> like the generated Ant build.
I guess we've already got that with the generated Ant build.
> > I just wondered; should the binary distro of maven projects come with a
lib
> > directory and all the jars they depend on? The source distro obviously
> > wouldn't need this - but non Maven or Ant users might like all the jars
> > inside an (admittedly large) binary distro?
> >
> > Right now the binary and source distros are pretty similar - maybe this
> > could be the main difference, the inclusion of dependent jars? Thoughts?
>
> I would like a target to get the JARs. Not sure how usable this would
> be. I just don't want to produce 100 distros nightly with tons of JARs.
> I would like to force the issue of reuse.
I understand and think you're right. Making this a default is probably a bad
thing (at least for Apache and their disk space ;-). So I'll keep this thing
local to Jelly's binary distro for now.
I guess I could refactor it into an optional goal that folks could attain if
they want to do that? e.g. if they are working on an internal project and
want to keep all the jars with the distro?
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
