Hi,
This make me think that maybe, there is 2 concepts hidden in the
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 packag
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 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 t
+1, sounds very interesting and I already face this "issue" a couple of times.
Stéphane
On 1/31/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
The assembly plugin has proven to be very valuable, and used very often.
Can we create a new type for "assembly" that defaults a set
of values, and eve
This sort of thing can be addressed in the assembly plugin itself
(though it requires 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 pr
0, 2007 6:31 PM
To: Maven Developers List
Subject: [PROPOSAL] Maven 2.1 assembly type.
The assembly plugin has proven to be very valuable, and used very often.
Can we create a new type for "assembly" that defaults a set
of values, and even provides standard artifact resolution
The assembly plugin has proven to be very valuable, and used very often.
Can we create a new 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 you
