[PROPOSAL] Maven 2.1 assembly type.

[Joakim Erdfelt <jo...@erdfelt.com>]

The assembly plugin has proven to be very valuable, and used very often.

Can we create a new <packaging> type for "assembly" that defaults a set
of values, and even provides standard artifact resolution during the
normal process.

Motivation is to have artifacts that are bundled/attached/assembled
during your build also be available to other modules in a standard maven
way, not through plugin hacks to pull them in outside of the normal
dependency resolution process.

Course, how do we rectify the multiplicity of types (tar.gz/tar.bz2/zip)?

I obviously haven't thought this through enough, but seeing as changes
like this are only really appropriate to a big version change such as
maven 2.1, it seemed like a good time to drop this idea on the rest of
you for comment.

- Joakim

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [PROPOSAL] Maven 2.1 assembly type.

[Stephane Nicoll <st...@gmail.com>]

+1, sounds very interesting and I already face this "issue" a couple of times.

Stéphane

On 1/31/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
> The assembly plugin has proven to be very valuable, and used very often.
>
> Can we create a new <packaging> type for "assembly" that defaults a set
> of values, and even provides standard artifact resolution during the
> normal process.
>
> Motivation is to have artifacts that are bundled/attached/assembled
> during your build also be available to other modules in a standard maven
> way, not through plugin hacks to pull them in outside of the normal
> dependency resolution process.
>
> Course, how do we rectify the multiplicity of types (tar.gz/tar.bz2/zip)?
>
> I obviously haven't thought this through enough, but seeing as changes
> like this are only really appropriate to a big version change such as
> maven 2.1, it seemed like a good time to drop this idea on the rest of
> you for comment.
>
> - Joakim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [PROPOSAL] Maven 2.1 assembly type.

[Raphaël Piéroni <ra...@gmail.com>]

Hi,

This make me think that maybe, there is 2 concepts hidden in the
<packaging/> element: project-kind and project-deliverable.

For example we could have a class library packaged in a jar file.
But we also could have that same class library packaged in a zip file.
Or we could have a java application packaged in a jar file.

Some project kinds are class library, aspect library, maven-plugin, web
application, desktop application.
Some project deliverables are jar file, war file, zip file.

Is this revelant or not?

Regards,

Raphaël

2007/2/6, Matt Brozowski <br...@opennms.org>:
>
>
> On Jan 30, 2007, at 6:38 PM, Brett Porter wrote:
>
> > This sort of thing can be addressed in the assembly plugin itself
> > (though it requires <extensions>true which is a bit gross, but
> > hopefully we can fix that in 2.1 anyway).
> >
> > I've thought about this before, but stumbled on the 'which type'
> > question.
> >
> > I think the real solution to this is to have plugins properly
> > expose the stuff they generate so that dependency resolution can
> > take it into account (also could be used from the dependency
> > plugin, for example).
> >
> > Doesn't discount the value of having such a packaging though (might
> > just need to have a <format> and <otherFormats> tags to make one
> > special :)
>
> I did something like this by making a tgz-plugin that calls assembly
> and used <packaging>tgz</packaging>
>
> I think its a great idea!
>
> Matt
> ________________________________________________________________________
> ___
> Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984
> The OpenNMS Group, Inc. Fax: +1 503 961 7746
> Email: brozow@opennms.org URL: http://www.opennms.com
>
>
>

Re: [PROPOSAL] Maven 2.1 assembly type.

[Matt Brozowski <br...@opennms.org>]

On Jan 30, 2007, at 6:38 PM, Brett Porter wrote:

> This sort of thing can be addressed in the assembly plugin itself  
> (though it requires <extensions>true which is a bit gross, but  
> hopefully we can fix that in 2.1 anyway).
>
> I've thought about this before, but stumbled on the 'which type'  
> question.
>
> I think the real solution to this is to have plugins properly  
> expose the stuff they generate so that dependency resolution can  
> take it into account (also could be used from the dependency  
> plugin, for example).
>
> Doesn't discount the value of having such a packaging though (might  
> just need to have a <format> and <otherFormats> tags to make one  
> special :)

I did something like this by making a tgz-plugin that calls assembly  
and used <packaging>tgz</packaging>

I think its a great idea!

Matt
________________________________________________________________________ 
___
Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984
The OpenNMS Group, Inc. Fax: +1 503 961 7746
Email: brozow@opennms.org URL: http://www.opennms.com

Re: [PROPOSAL] Maven 2.1 assembly type.

[Brett Porter <br...@apache.org>]

This sort of thing can be addressed in the assembly plugin itself  
(though it requires <extensions>true which is a bit gross, but  
hopefully we can fix that in 2.1 anyway).

I've thought about this before, but stumbled on the 'which type'  
question.

I think the real solution to this is to have plugins properly expose  
the stuff they generate so that dependency resolution can take it  
into account (also could be used from the dependency plugin, for  
example).

Doesn't discount the value of having such a packaging though (might  
just need to have a <format> and <otherFormats> tags to make one  
special :)

- Brett

On 31/01/2007, at 10:31 AM, Joakim Erdfelt wrote:

> The assembly plugin has proven to be very valuable, and used very  
> often.
>
> Can we create a new <packaging> type for "assembly" that defaults a  
> set
> of values, and even provides standard artifact resolution during the
> normal process.
>
> Motivation is to have artifacts that are bundled/attached/assembled
> during your build also be available to other modules in a standard  
> maven
> way, not through plugin hacks to pull them in outside of the normal
> dependency resolution process.
>
> Course, how do we rectify the multiplicity of types (tar.gz/tar.bz2/ 
> zip)?
>
> I obviously haven't thought this through enough, but seeing as changes
> like this are only really appropriate to a big version change such as
> maven 2.1, it seemed like a good time to drop this idea on the rest of
> you for comment.
>
> - Joakim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org