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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
