On 1 January 2017 at 04:42, Christian Schulte <c...@schulte.it> wrote:
> Am 12/31/16 um 21:10 schrieb Stephen Connolly: > > Here are the changes in current master since 3.3.9 (with some minor > changes > > omitted) > > > > Issue ID Target Version Summary > > ======== ============== ============================================ > > MNG-1577 WONTFIX dependencyManagement does not work for > > transitive dependencies > ^ > FIX-3.6.0 > > > MNG-2199 WONTFIX Support version ranges in parent elements > ^ > FIX-3.5.0 > -1: I propose FIX-3.5.1 as this makes it hard for 3.5.0 to be a drop in behaviour replacement fort 3.3.9 > > > MNG-4463 WONTFIX Dependency management import should support > > version ranges. > ^ > FIX-3.6.0 > > > MNG-5227 WONTFIX The 'optional' flag of a dependency should > > be manageable. > ^ > FIX-3.6.0 > > > MNG-5359 WONTFIX Declared execution in PluginMgmt gets bound > > to lifecycle (regression) > ^ > FIX-3.5.0 > -1: I propose FIX-3.5.1 as this makes it hard for 3.5.0 to be a drop in behaviour replacement for 3.3.9 > > MNG-5527 WONTFIX Relocation does not work for imported poms > ^ > FIX-3.6.0 > > > MNG-5600 WONTFIX Dependency management import should support > > exclusions. > ^ > FIX-3.6.0 > > > MNG-5629 WONTFIX ClosedChannelException from > > DefaultUpdateCheckManager.read > ^ > FIX-3.5.0 > I'll second > > > MNG-5761 WONTFIX Dependency management is not transitive. > ^ > FIX-3.6.0 > > > MNG-5935 WONTFIX Optional true getting lost in managed > > dependencies when transitive > ^ > FIX-3.6.0 > > > MNG-5958 WONTFIX restore binary compatibility of > > Lifecycle.setPhases > ^ > FIX-3.5.0 > Already marked as agreed > > > MNG-5971 WONTFIX Imported dependencies should be available to > > inheritance processing > ^ > FIX-3.6.0 > > > > MNG-6023 WONTFIX Upgrade of slf4j-simple to a version later > > than 1.7.16 blocked by upstream issue. > ^ > FIX-3.5.0 > Explain why we need to update the slf4j dependency in 3.5.0 and not 3.5.1 > > That's a duplicate to the "Dependency updates" JIRA issue. > > > MNG-6049 WONTFIX Add behavior to filter resolved version > > ranges of an artifact > ^ > FIX-3.6.0 > > I am not sure about the solution to this one currently on master. It > adds an interface we already have in the resolver but do not expose in > Maven core. Maybe this needs re-thinking. Better solution would be to > allow core extensions to provide various components for the > "RepositorySystemSession". Setup of the repository system currently is > done in a static method. This would need to be changed to support core > extensions. > > > MNG-6053 WONTFIX guard against key without value > ^ > FIX-3.5.0 > > > MNG-6053 WONTFIX prevent NPE when copying System Properties > > in MavenRepositorySystemUtils > ^ > FIX-3.5.0 > I'll second this one > > > MNG-6073 WONTFIX Addition of a core extension point to the > > model builder supporting model finalization. > ^ > FIX-3.6.0 > > > MNG-6074 WONTFIX Maven should produce an error if no model > > version has been set in a POM file used to > > build an effective model. > ^ > FIX-3.5.0 > -1: I propose WONTFIX or FIX-3.6.0 if the issue is changed to outputting a warning rather than an error > > > MNG-6075 WONTFIX Increase the model validation level to the > > next minor level version. > ^ > FIX-3.6.0 > > > MNG-6079 WONTFIX 3.4 regression: cannot override version of > > a dependencyManagement in a submodule any > > more > ^ > FIX-3.6.0 > > > MNG-6105 WONTFIX properties.internal.SystemProperties > > .addSystemProperties() is not really > > thread-safe > ^ > FIX-3.5.0 > I'll second > > Related to MNG-6053. > > > MNG-6112 WONTFIX Central repository in the 4.0.0 super POM > > should declare update policy 'never'. > ^ > FIX-3.5.0 > -1 for 3.5.0. I need to think some more about where this should land > > > MNG-6113 WONTFIX Rename the 'Central Repository' to > > 'Maven Central Repository' in the 4.0.0 > > super POM. > ^ > FIX-3.5.0 > -1 for 3.5.0. I need to think some more about where this should land > > > MNG-6114 WONTFIX Profiles from the global settings should be > > ordered before profiles from the user > > settings. > ^ > FIX-3.5.0 > -1 for 3.5.0 as it prevents being a drop in replacement for 3.3.9. I am open to putting this in either 3.5.1 or 3.6.0 > > > MNG-6135 WONTFIX Maven plugins and core extensions are not > > dependencies, they should be resolved the > ^ > FIX-3.6.0 > > > MNG-xxxx WONTFIX Updated to ensure 'MavenProject. > > getManagedVersionMap()' consistently > > returns an immutable map. > ^ > FIX-3.5.0 > Can we get a JIRA to cover this immutable issue > > > MNG-xxxx WONTFIX Updated to ensure collections are immutable > > consistently. > ^ > FIX-3.5.0 > Should be the same JIRA as above > > > MNG-xxxx WONTFIX Updated to make the > > 'JavaDependencyContextRefiner' part of the > > dependency graph transformer lost in > > commit > > 3916201b985c281a2b073b9b764bbb554584f5a7. > ^ > FIX-3.5.0 > Given that the referenced commit was present in Maven 3.1.0+ I think including this would break drop-in replacement for 3.3.9. On that basis I am -1 for 3.5.0. I think this could go FIX-3.5.1 > > MNG-xxxx WONTFIX Updated to remove various Javadoc warnings. > ^ > FIX-3.5.0 > If this is Javadoc only changes i.e. not affecting code, then I'll second... You'll need to create a JIRA > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
