> > Hi, Hi,
> > We discussed this briefly before. From looking at that, this > seems to be the most workable solution: > - for any new features added in m1 or m2, we add a > description to the plugin site so that we have a comparitive checklist +1, I'll try to do it as soon as possible in plugins I use(d). > - for any bugs fixed in m1 that potentially impact m2, when > fixed, clone the issue and move it to the other project, > linking the original (this should only be a small % of issues > as they usually relate to jelly-isms, > etc) - this would include minor features (ie other options or > configurations). Who can do that ? I think it will concern only updates and new features on plugins (bugs are not significant because m2 plugins were totally rewriten from scratch). But actually I don't know which features are done in m2 plugins (and it'll take me some time to know them). Are there some m2 committers who can follow the issues we close in m1 ? > > Of course, the best solution where practical is to have them > share the code (eg JXR). YES. +1000 ;-) > > My main concern is that all the great work Lukas, Arnaud and > Carlos have done recently would need to be duplicated later > and hard to track. Yes I know :-( but I don't have another solution to release maven 1.1 before m2 ;-). We don't have the time and people to try to reuse plugins between m1 and m2 (unfortunately). > > Does this sound ok? Ok for me. Arnaud > > - Brett > > --------------------------------------------------------------------- > 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]
