I'll can reply in more detail when I get a chance if needed, but I don't think this is the right approach.
Two reasons: 1) branching/versioning should be on a per-plugin level, if needed 2) changes should be backwards compatible at this stage, indicating that a branch may not be needed. IIRC this is the change to a new .final.name property. I think if you put some code in to set it, and if not set get it from the old property name, it should play nicely. I did similarly in the artifact/deploy plugin. Cheers, Brett Quoting Felipe Leme <[EMAIL PROTECTED]>: > Hi all, > > I'd like to fix issue MPJAVA-8 > (http://jira.codehaus.org/browse/MPJAVA-8) but in order to do so I will > need to change many plugins and hence the fix itself will take a while > (as I will have to write new test cases for each affected plugin). > > So, I was thinking about working on a separate branch while this issue > is fixed. If the documentation - > http://maven.apache.org/development/branches.html - is up-to-date (looks > like it is from the Maven/Turbine days), I would need to create on > maven-plugins a MPJAVA8_SPROUT tag and a MPJAV_8_BRANCH branch before I > start the work and then the MPJAVA8_BEFORE_MERGE and MPJAVA8_MERGE tags > afterward. > > > Is that right? If so, can I go ahead and do the changes? > > -- Felipe > > > > > > --------------------------------------------------------------------- > 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]
