Yes, this definitely helps, Stephen. Thanks for your detailed and well-written explanation. I appreciate it much.
Cheers, Paul On Wed, Dec 17, 2014 at 9:22 AM, Stephen Connolly < [email protected]> wrote: > > On Wednesday, December 17, 2014, Paul Benedict <[email protected]> > wrote: > > > Stephen, I don't feel strongly about it but I don't think there is > another > > option. Unlike assembly:single which is used to create multiple > > distributions, this is about creating an artifact destined to be consumed > > as a dependency. Correct me if wrong, but Maven artifact types are meant > to > > produce one single/prime artifact, otherwise you have to begin specifying > > "type" element on your dependencies. > > > No you have it wrong there. > > Type defaults to `jar` if unspecified, so you will need to declare a type > to consume either the zip or tar.gz > > The only case I know of where you get away from that is the horrible hack > in jenkins plugins where you depend on the jar and the hpi plugin > up-interprets the actual type from the resolved pom so that hpi > "dependencies" are linked at runtime and non-hpi dependencies are packaged > in WEB-INF/lib > > Most of the other packaging types produce jar files and use the packaging > to determine the lifecycle > > Having said all that, the *default* descriptor should be just a zip... But > if you override the default you can have a descriptor that produces .tar.gz > and .tar.bz2 as well as .zip > > So I would say that the mojo should: > > * use its default descriptor if none in src/assembly > > * use the descriptor if one and only one in src/assembly > > * fail if more than one descriptor in src/assembly unless the user adds > config to say which one to use > > HTH > > >
