> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Monday, April 18, 2005 11:06 PM > To: Maven Developers List > Subject: Re: [M2] filter definition > > > Maczka Michal wrote: > > >I a not 100% sure if I understand you. > >What do you mean by deployment process here? Is it going to be > >supported/executed in m2? > > > > > Yes, what we were talking about covers your use case, you'd > just need to > run your deployment profiles over the artifacts and store > them wherever > is suitable to later retrieve them and distribute them. > > Maybe a layered repository approach would be helpful here, where you > copy the relevant artifacts to change and build a small repository of > them that they can use, and for the standard stuff the base repository > is used. > > Just thinking out loud, but it all fits together with what we > were thinking. >
I think all this is already supported in m2. For each artifact you can already choose to which repository it will be deployed so it is up to users to organize repository systems as they wish :). Only missing parts are plugins which will mutate artifacts. Your assemble plugin is really very good example which shows the way in which such plugins could be written. I don't think that much more is needed :) reagrds michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
