The following issues IMHO all affect build time behaviour and do not affect dependency consumption. As such they do not require a modelVersion bump
https://issues.apache.org/jira/browse/MNG-6054 https://issues.apache.org/jira/browse/MNG-5992 https://issues.apache.org/jira/browse/MNG-5968 https://issues.apache.org/jira/browse/MNG-5940 https://issues.apache.org/jira/browse/MNG-4645 https://issues.apache.org/jira/browse/MNG-2478 The following issues affect dependency consumption, but IMHO could be considered as bug fixes rather than RFEs. Strictly speaking they involve behaviours that we have never specified and thus it is questionable as to whether they are deviating from the original intent (in which case they would be RFEs and warrant a modelVersion bump) or whether they align with the original intent (which makes them bugs and not requiring of a modelVersion bump) https://issues.apache.org/jira/browse/MNG-5527 - clearly a bug https://issues.apache.org/jira/browse/MNG-4463 - clearly a bug https://issues.apache.org/jira/browse/MNG-5600 - less clear, import scope itself should probably have required a modelVersion bump or at least a clear specification, but that ship has sailed... this new behaviour aligns with the unspecifiied expectations I would have of how a scope and exclusions would work, so IMHO that makes it a bug That just leaves: https://issues.apache.org/jira/browse/MNG-5971 I would argue that the behaviour change in MNG-5971 should not be introduced at the same time as a refactoring to move to the new "code formerly known as Eclipse Aether but now at Apache under a different name" codebase. So, in short, I think of the 10 issues, only one "potentially" qualifies as perhaps maybe requiring a modelVersion bump, and I would not want that included with the other changes for 3.4.x anyway On 10 October 2016 at 09:26, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On 10 October 2016 at 01:38, Christian Schulte <schu...@apache.org> wrote: > >> Am 10/09/16 um 21:44 schrieb Stephen Connolly: >> > Open issues bound to 3.4.0 >> > >> > * Introduction of model version 4.1.0. >> > https://issues.apache.org/jira/browse/MNG-6082 >> > <https://issues.apache.org/jira/browse/MNG-6082> >> > assignee: Christian Schulte (reporter: Christian Schulte) >> > >> > >> > I am -1 on this change as I understand it as it will break central for >> > older consumers. >> >> That's why I asked what I should do about it. I can easily >> revert/disable things. I thought we are not going to release 3.4 but 4.0 >> with the new model version and PDT support, no? So there will be a 3.4 >> release? Please see all the issues MNG-6082 is linked to. Not bumping >> the model version means disabling almost all of the changes done for >> those issues. I'd really would not want to do that. Yes. Model version >> 4.1.0 will never get released. I got that. I thought we are already >> working on model version 5.0.0 / PDT and that will make shipping those >> changes possible. >> > > Well we need to decide what to do now about cutting a release with the > code formerly known as Eclipse Aether at its new home... which AIUI is what > 3.4.0 would be. > > We cannot ship anything that deploys a pom with a modelVersion other than > 4.0.0 IMHO as that would require forking the central repository. > > There is still some work to be done on getting the proposals for how to > move forward safely... and I am not seeing much engagement with the work I > have been trying to do... which scares me somewhat... > > If we need to unwind some of the changes you made that required a > modelVersion bump then I think we need to do that... but I am not seeing > others chime in on this topic either... > > >> >> Regards, >> -- >> Christian >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >
