remember: we'll have to explain users why we did a breaking change
I don't think such an explanation will be possible for users: for long-dev 
like me, it's hardly a valid explanation

Can you explain in plain english some cases, please?

And remember we'll require to prepare a list of known plugins

When fixing the code means breaking user builds at large scale (which I fear is 
the case here), there is change management to prepare: the team can help, but 
you need to help the team first

Regards,

Hervé

Le mercredi 21 décembre 2016, 02:45:05 CET Christian Schulte a écrit :
> Am 12/20/16 um 08:06 schrieb Hervé BOUTEMY:
> > I must confess I never investigated why this "provided" recipe worked: it
> > just looked nice :)
> > 
> > but you didn't answer the important part of the question:
> > From a purist point of view, I understand
> > From a user point of view, do you have any case where the new behaviour
> > fixes a non-working configuration (instead of breaking a build that was
> > working previously)?
> 
> The issues in JIRA currently fixed on master do have example projects
> attached. Those are what started this. Some of them became ITs.
> 
> ~/Sources/apache.org/maven-integration-testing/core-it-suite
> $ grep -ri "\[3\.4" *
> src/test/java/org/apache/maven/it/MavenITmng1701DuplicatePlugin34Test.java:
>        super( "[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng3843PomInheritanceTest.java:
>        if ( matchesVersionRange( "[3.4,)" ) )
> src/test/java/org/apache/maven/it/MavenITmng5889CoreExtensionsTest.java:
>        super( "[3.4.0,)" );
> src/test/java/org/apache/maven/it/MavenITmng3719PomExecutionOrdering34Test.j
> ava: super( "[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng4005UniqueDependencyKey34Test.ja
> va: super( "[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng4463DependencyManagementImportVe
> rsionRanges.java: super( "[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng5227DependencyOptionalFlagManage
> mentTest.java: super( "[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng5359CleanPluginExecutionDeclarat
> ionInPluginMgmtTest.java: super( "[2.0.11,3.0-alpha-1),[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng5527DependencyManagementImportRe
> locationsTest.java: super( "[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng5600DependencyManagementImportEx
> clusionsTest.java: super( "[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng5971HierarchicalImportScopeTest.
> java: super( "[3.4,)" );
> src/test/java/org/apache/maven/it/MavenITmng6084Jsr250PluginTest.java:
>      super( "[3.4.0-SNAPSHOT,)" );
> src/test/java/org/apache/maven/it/MavenITmng6127PluginExecutionConfiguration
> InterferenceTest.java: super( "[3.4.0,)" );
> src/test/java/org/apache/maven/it/MavenITmng4720DependencyManagementExclusio
> nMerge34Test.java: super( "[3.4,)" );
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to