Sorry, what I meant was what has Maven learned about managing plugins? As Martin pointed out, it can easily become scattered and confusing for users, but on the other hand, opening up plugins for outside contributions let's us focus on the core of Struts 2. How does Maven ensure the support of popular plugins?
Don On 8/20/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 8/19/07, Don Brown <[EMAIL PROTECTED]> wrote: > > > Agreed, Spring should be a first-tier plugin. I'm fine with spinning > > off the others, but who would maintain them? If it will be the same > > people, then perhaps we should keep them in the repository. > > > > How does Maven handle this situation? Wendy? > > How does Maven handle what? Ted seems to be talking about moving > these plugins out of 'trunk' -- so presumably to sandbox or out to > another place entirely. You'll need to take them out of the <modules> > list, and adjust the assembly descriptors for the release > distributions. > > -- > Wendy > > --------------------------------------------------------------------- > 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]
