For me the first thing is to push some ideas in the wiki and make them challenged by developpers I'm not so sure that there is a consensus and a real proposal to solve that upgrade taking care of all use cases (previous/future versions of maven, transitive dependencies, depMgt import, inheritence ...) The thing said by everybody is that we won't be able to change the format/version of *.pom files in shared repositories but I saw no real proposal to manage all cases listed above when we'll have several versions of POMs out (even if we just add new entries).
Arnaud On Sun, Jul 17, 2011 at 11:33 PM, Benson Margulies <[email protected]>wrote: > Many threads lead back to the recent discussion, and all of its > predecessors, about preparing for a new version of the pom by allowing > for backwards compatibility. > > How do we start this? There seemed a consensus on the design. Do we > need some branches of things? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
