This may be throwing gasoline onto an already burning fire but a thought occurred to me over the weekend, if we're going to go to the extend of changing the POM formats, this quite majorly affects repository browsers/servers/indexers etc.
I was wondering if this doesn't also require a change in the repository type as well ( I need to read thru all the threads to see whats been suggested or not ), are we planning to mix/match the new poms with the old? I was also thinking it might be timely to rematch various videos about problems with maven, sbt, gradle and even maybe totally rethink the repository layout, servers etc. etc. of course, thats a much more epic set of changes ;p On 2 Dec 2013, at 6:07, Brian Fox wrote: > It means we can more easily make changes to the production side, where most > features are desired, without worrying about the impacts on consumption via > older tools. That is to say specifically that a team can decide to move to > a new version of Maven and adjust their pom accordingly without affecting > downstream users. I think this is the very reason we are still locked on > 4.0.0 all these years later.
signature.asc
Description: OpenPGP digital signature
