Can the assembly plugin take part in the normal lifecycle in the current release (in the past it couldn't)? As I see it, that is a stumbling block for a lot of people. If this can't or won't be changed, then spinning off some limited functionality into a separate mojo may make sense.
-----Original Message----- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, January 02, 2006 6:28 AM To: Maven Developers List Subject: Re: archiver-maven-plugin? On 1/2/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > dan tran wrote: > > On 1/2/06, Brett Porter <[EMAIL PROTECTED]> wrote: > >> dan tran wrote: > >>> 2. Descriptor's objects are exposed through plugin's configuration. > >>> This way, we can take advantage of expression processing > >>> provided > >> by > >>> the POM. > >>> > >> I think we need to introduce this to the assembly plugin anyway. > > > > > > Sound good, is it thru a seperate mojo? > > No, I think the existing mojo needs to interpolate the descriptor. OK, let me see what I can do!! > I think most user need is the capablity to assembly files and > dendencies > > together. > > This is exactly archiver-maven-plugin provides ( exception the > dependencies > > ). > > The maven-assembly-plugin has a rich set of features that I think It > will > > take for ever > > to release. > > I still don't understand. The assembly plugin is already released! :) > Do you mean the wait for the 2.1 release? It has been 2 and half months. ;-) Is it time a for a new release? Any how, I agree that It does not look right when there are 2 similar plugins. - Brett > > --------------------------------------------------------------------- > 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]
