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 -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 8:20 PM To: 'Maven Developers List' Subject: RE: 1.0, 1.1 and branches - Status? Are they doing 1.1 only plugins? If the decision to break compatibility with 1.0 is made, then they do the same thing - dev their new versions on maven-plugins/plugin-name HEAD, and branch the old one only for 1.0 compatible bugfixes. I think that would be a crazy decision to make on behalf of the plugin owner, as there'll be no public releases of 1.1 for a long time yet. I don't see any need for people to break 1.0 compatibility inside a plugin right now. If they need POM v4 features, there are conditionals to do it. Branching the entire maven-plugins tree is a statement that the plugin development is again tied to Maven, which just isn't the case. Cheers, Brett > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 25 November 2003 12:21 PM > To: Maven Developers List > Subject: RE: 1.0, 1.1 and branches - Status? > > > I still don't see how people are going to do 1.1 plugins > without applying > the same branches to maven-plugins. > > Shouldn't both modules have the same set of branches created? > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
