Jason van Zyl <[EMAIL PROTECTED]> wrote on 17/04/2002 11:28:14 AM: > On Tue, 2002-04-16 at 21:37, [EMAIL PROTECTED] wrote: > > The <jars> project descriptor element seems a bit misplaced given the > > current docs. It is supposedly for including jars into other jars - what > > the? > > It's a vestige of the gump descriptors: it represents the JARs produced > by a build. But if the project is 'normalized' then maybe it should only > produce a single JAR. And these are used in gump to produce a path to > the produced JAR so it's available when building other projects. > > > It does however make sense to have these as things that are included into > > the dist jar, i.e. a project wants to ship jars that are not dependencies > > (and who knows what those are), as part of the binary distribution. > > > > Could we repurpose the tag for that functionality?
Ok, I need some stuff placed in the dist dir as part of the 'dist' processing. Maybe we could add a dist.basedir property as well, like the jarResources.basedir? This is for stuff like shell scripts, batch files etc... -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers
