2008/1/9, Brian E. Fox <[EMAIL PROTECTED]>: > How was it resolved in 2.1? If there is a new zip plugin, will that > conflict with the 2.1 solution? (we'll end up supporting it forever). > And why not just a new goal to the assembly plugin?
It's marked as solved in trunk but not sure it's really fixed. Just tested with a sample projet (zip packaging) with current trunk and no artifact is produced. When you talk about "2.1 solution", what is this ? (can you give me any link to this ?). Right we have the assembly hack. (but I agree here on the Vincent's comment [1]) And as it's a hack, users need to had some extra plugin configuration to attach his real artifact (because the real needed artifact is a zip and not a pom). Thanks, -- Olivier [1] http://jira.codehaus.org/browse/MNG-1683#action_85816 > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Olivier Lamy > Sent: Wednesday, January 09, 2008 4:06 PM > To: Maven Developers List > Subject: Zip packaging in 2.0.x (MNG-1683) > > Hi, > I have just read a thread [1] on the user mailing list. > Is there any objections if I reopen the issue [2] and fix it in the > 2.0.x branch ? > A new plugin (maven-zip-plugin) will be added too. > > Thoughts ? > > Thanks, > -- > Olivier > > [1] > http://www.nabble.com/Existance-of-ZIP-Archetype--%7C-How-to-distribute- > DB-code-to-different-mvn-modules--td14614465s177.html > [2] http://jira.codehaus.org/browse/MNG-1683 > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
