Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

Am 12/24/16 um 17:59 schrieb Hervé BOUTEMY: > +1 > > notice that it may show that we have an issue with the way transitivity + > nearest resolution are applied > > IIUC this case, we have: > 1. a direct dependency with scope = test > 2. a transitive dependency with scope = compile > > the resul

Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

Am 12/24/16 um 18:40 schrieb Guillaume Boué: > Why would the PMD plugin care about what Doxia require transitively? > Christian, can you explain a bit more why those changes are needed? Classpath consistency. Running the unit tests with a completely different classpath than what the plugin is usi

Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

Am 12/24/16 um 17:03 schrieb Robert Scholte: > With this commit commons-io gets the default scope. > Suppose PMD drops commons-io, then there's no reason that this dependency > has the compile scope. > Assuming the unittests are using commons-io it makes sense that it has the > test-scope. Put

Re: Roadmap to the next Maven release (Re: Improving Jenkins)

Le samedi 24 décembre 2016, 18:33:06 CET Guillaume Boué a écrit : > Yes, I agree with this. The plugin doesn't need to inspect its own > annotations at runtime, so the dependency is "only needed at > compile-time, unused at run-time". The provided scope may be a bit of an > abuse for lack of a "com

Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

Why would the PMD plugin care about what Doxia require transitively? Christian, can you explain a bit more why those changes are needed? Le 24/12/2016 à 17:59, Hervé BOUTEMY a écrit : +1 notice that it may show that we have an issue with the way transitivity + nearest resolution are applied

Re: Roadmap to the next Maven release (Re: Improving Jenkins)

Le 24/12/2016 à 17:11, Hervé BOUTEMY a écrit : Le vendredi 23 décembre 2016, 09:32:50 CET Christian Schulte a écrit : Am 12/23/16 um 08:16 schrieb Hervé BOUTEMY: Le vendredi 23 décembre 2016, 03:59:17 CET Christian Schulte a écrit : Am 12/22/16 um 19:14 schrieb Robert Scholte: -0.9 for the

Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

+1 notice that it may show that we have an issue with the way transitivity + nearest resolution are applied IIUC this case, we have: 1. a direct dependency with scope = test 2. a transitive dependency with scope = compile the result can't be just the direct dependency with scope=test: scope of

Re: Roadmap to the next Maven release (Re: Improving Jenkins)

seriously, you should make an effort to improve description of the failures caused by the MRESOLVER-8 bugfix (which AFAIK only causes breaks: not so many, but only breaks currently, so it's hard to call MRESOLVER-8 a real fix...) Regards, Hervé Le samedi 24 décembre 2016, 15:58:20 CET Christia

Re: Roadmap to the next Maven release (Re: Improving Jenkins)

Le vendredi 23 décembre 2016, 09:32:50 CET Christian Schulte a écrit : > Am 12/23/16 um 08:16 schrieb Hervé BOUTEMY: > > Le vendredi 23 décembre 2016, 03:59:17 CET Christian Schulte a écrit : > >> Am 12/22/16 um 19:14 schrieb Robert Scholte: > >>> -0.9 for the commandline option, there should be on

Re: svn commit: r1775971 - /maven/plugins/trunk/maven-pmd-plugin/pom.xml

With this commit commons-io gets the default scope. Suppose PMD drops commons-io, then there's no reason that this dependency has the compile scope. Assuming the unittests are using commons-io it makes sense that it has the test-scope. Be aware that users can overwrite dependencies of plugins

Re: Roadmap to the next Maven release (Re: Improving Jenkins)

maven-pmd-plugin >= 3.4 is affected. - To unsubscribe, e-mail: dev-unsubscr...@maven.a

Re: Roadmap to the next Maven release (Re: Improving Jenkins)

maven-resources-plugin < 3.0.2 also is affected. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Releasing Wagon 2.11

Am 2016-12-24 um 04:07 schrieb Dan Tran: Hi, We have fixed 18 issues: *https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=1296 * There are still issues left in JIRA: *h