A subject change such as this is probably a best practice for such a case. There are a few references around on netiquette which should help, but I don't have any to hand.
As far as plugin development being separate, each can be released, versioned and downloaded independantly of maven itself, so you can update just the WAR handling code for example, without waiting for a big release of Maven itself with tends to take a while. Cheers, Brett > -----Original Message----- > From: Aaron Anodide [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 25 November 2003 12:26 PM > To: 'Maven Developers List' > Subject: RE: 1.0, 1.1 and branches - Status? > > > I'm not sure the best practices of posting to mailing lists, > as I'm new to them.. it seems you pretty much have to top > post all the time, right? > > That said, I'm interested in your last point. How is maven > plugin development separated from the maven core, architecturally? > > Thanks Alot, > Aaron >
