Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
MIME-Version: 1.0
In-Reply-To: 
 <CA+nPnMxb4TH6WixKWQjb1kDSi4AaH+mBi0Ooc2Zc_scZOpypUw@mail.gmail.com>
References: 
 <CABLGb9z8eVOpxCc7A-f_1aYiChY2Jq5uawtyqMZhttD5Gh2DLg@mail.gmail.com>
	<CAJZRQKz1SbM4878MeA70OiCDZqkOW008WAauGJYZkC6iMAYLNQ@mail.gmail.com>
	<CABLGb9zyiKMFokUE9JpG1QTY2Ah7T0xrmMTmGj5uqEsM3_kFNQ@mail.gmail.com>
	<CAKDUN1sqsGV-DmqLKWjE3DRKkNdZ3+0NHYLQiXNtt62Q83j=wg@mail.gmail.com>
	<CABLGb9xV1cxPfL3t+8kHcOh9yG4o0EUDW4xh3HYzhZWQGzC9fw@mail.gmail.com>
	<CAKDUN1tJFozmZM5fab=p7v5SfwJddcEi+0YEa2rtSrk5TXhqbw@mail.gmail.com>
	<CA+nPnMyC7XLSpP+DooH-6+Pg4TnE1DD2LWo=jWHvovoVzroh4g@mail.gmail.com>
	<F7B85D5D-DF43-41FF-8AE1-72C7AE9F7E3E@fortysix.ch>
	<54899B72.6070802@caris.com>
	<CA+nPnMzzPhJ=B2+TDoqgn6O5LHtChkPfoC7Gd2WxaUbc4dsxoQ@mail.gmail.com>
	<CABLGb9zHAN1k5q+LZFKfkC0xL+RR6zCFXaC0gJHmZeEQ3d=VfA@mail.gmail.com>
	<CA+nPnMzVWUwHYE2HKDy_CxwWqBcE1V-_seg3SRC6X_SN_DUVGA@mail.gmail.com>
	<20141216172534.7B0AE4340BED@dd34514.kasserver.com>
	<CABLGb9wA6hG1Ujp7hYRq8VAfVCADxaKuag2J8mOwnkc0NvTv0Q@mail.gmail.com>
	<CA+nPnMwUXBk6uoPoqD3M3oZewLj1ngsLcke-4c_9KLKmZg34EQ@mail.gmail.com>
	<CABLGb9yuFd3c61RB47ckmgfTS0pC-OU_Z2m+-8ay8D2+2Ack1w@mail.gmail.com>
	<CA+nPnMxb4TH6WixKWQjb1kDSi4AaH+mBi0Ooc2Zc_scZOpypUw@mail.gmail.com>
Date: Wed, 17 Dec 2014 20:32:47 -0600
Message-ID: 
 <CABLGb9w2jgARPkAvT6DsJ0MxJM0k0BsHr15isbqOhNs7FRm0Nw@mail.gmail.com>
Subject: Re: MNG-1683: Zip packaging
From: Paul Benedict <pbenedict@apache.org>
To: Maven Developers List <dev@maven.apache.org>
Content-Type: multipart/alternative; boundary=089e0149cfa4688329050a746833

--089e0149cfa4688329050a746833
Content-Type: text/plain; charset=UTF-8

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 <
stephen.alan.connolly@gmail.com> wrote:
>
> On Wednesday, December 17, 2014, Paul Benedict <pbenedict@apache.org>
> 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
>
>
>

--089e0149cfa4688329050a746833--