>-----Original Message----- >From: Phillip Hellewell [mailto:[email protected]] > >On Fri, Oct 1, 2010 at 4:23 PM, Jon Paynter <[email protected]> wrote: >> Glad it has helped. >> >> but id still like to know why unpack-dependencies tries to unpack a pom >file > >Well I did have <type>pom</type> in my dependency in the dependencies >section. But yeah, it still shouldn't try to unpack a pom. Perhaps >it is a bug?
er... well unpack-dependencies is supposed to unpack things, and you were explicitly giving it a pom type artifact, so it seems like it was doing approximately what it should. I'm thinking of this setup as a (more verbose) way of saying: jar -xf pom.xml Looking at it from another point of view, what *should* it do with a pom artifact? Simply copying it seems wrong, since there's an explicit copy-dependencies goal for doing that. I don't think I'd consider this a bug. eric --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
