On Mon, Oct 4, 2010 at 9:30 AM, Haszlakiewicz, Eric <[email protected]> wrote: > > 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.
It could copy it or just skip it, but giving an error could be problematic. How about a warning instead? Consider this scenario. What if I had a "pom" artifact that didn't include a zip or jar or anything, but I need to depend on it because I need to get everything it depends on, and I want those dependencies to get unpacked? Phillip --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
