why not just use the zip ant tasks. The ear and war tasks are really just fancy zip tasks. Then you could use a mapper. If you're really keen, you could create some ant macrodefs <ivycache:war> and <ivycache:ear> that look like the ant war and ear tasks, but actually use zip.
On Mon, Feb 11, 2008 at 12:30 PM, limbicsystem <[EMAIL PROTECTED]> wrote: > > Hi, > > I have a very large build with hundreds of artifacts. In order to create > war and ear files with their dependent libs in the right place (typically > WEB-INF/lib), I create a temporary "staging" dir, copy in the dependencies > from cachefileset, and then create the war/ear. This works, but is very > slow due to all the copying. > > I can get a significant speedup if I use the fileset references created by > ivy:cachefileset directly when creating the war. This avoids the > intermediate copying of the dependencies. It works, but I am unable to > specify the proper location of the libs inside the resulting war/ear, as > they have full paths like > $HOME/.ivy2/cache/organisation/module/jars/foo-1.2.3.jar. Unfortunately > the > war/ear tasks do not take <mapper> arguments. > > This is not really an Ivy problem, but I imagine other Ivy users have run > into this. I'm considering writing a ZipFileSet extension to address > this, > but would prefer to use an existing solution if there is one. > > Thanks, > L > > -- > View this message in context: > http://www.nabble.com/using-cachefileset-for-creating-war-files-without-staging-dir-tp15405054p15405054.html > Sent from the ivy-user mailing list archive at Nabble.com. > > -- Regards, John Gill
