> So each plugin directory inside maven-plugins will have it's > own branches? > That's going to be very hard to manage if I'm developing on multiple > plugins isn't it? >
I think it's a non-issue. It should be rare that a plugin does some development that makes it 1.1 only AND decides to maintain a separate version for 1.0 compatibility. > > Branching the entire maven-plugins tree is a statement that > the plugin > > development is again tied to Maven, which just isn't the case. > > I agree, but we're going to need a consistent, agreed way to > handle it. If its good for maven, it should be good for the plugins I think. It's the same technique that is used in projects such as Tomcat, Struts, mozilla, and any number of others that have multiple release streams. It's consistent, and as long as it is documented (this is what <branches> is in the POM for, right? :) I don't think there'll be an issue. Cheers, Brett
