Re: Commits 02795b21e753bdd4eddd7e9ebee9f50315bc0e24 and 3681fd8489cd59d0c5bc49ef38725b655d524301

We first need to decide on the version this will get released as. Updating everything to 3.4 now and to 4.0 two weeks later I can avoid the duplicate effort this time. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org

Re: Maven 3.4.0 Release

Am 12/17/16 um 05:17 schrieb Christian Schulte: > Am 12/12/16 um 00:51 schrieb Igor Fedorenko: >> I'm traveling until next weekend and won't be able to review your changes >> properly until I'm back. I do want to stress that maven plugins are not >> dependencies, they are resolved the same way

Re: Maven 3.4.0 Release

Am 12/12/16 um 00:51 schrieb Igor Fedorenko: > I'm traveling until next weekend and won't be able to review your changes > properly until I'm back. I do want to stress that maven plugins are not > dependencies, they are resolved the same way as projects. Master does it that way now. I may need

Improving Jenkins

Hi, I renamed the 'maven-aether-provider' module to 'maven-resolver-provider'. What happens on Jenkins is this: The 'maven-aether-provider' folder will not get deleted correctly when Jenkins performs the SCM update/checkout. This may be due to the existence of the 'maven-aether-provider/target'

Re: Commits 02795b21e753bdd4eddd7e9ebee9f50315bc0e24 and 3681fd8489cd59d0c5bc49ef38725b655d524301

Am 12/16/16 um 21:36 schrieb Michael Osipov: > Am 2016-12-16 um 18:41 schrieb Christian Schulte: >> Am 12/15/16 um 22:49 schrieb Michael Osipov: >>> I would expect a VALIDATION_LEVEL_MAVEN_3_4 with VALIDATION_LEVEL_STRICT >>> = VALIDATION_LEVEL_MAVEN_3_1. All spots which say Severity errOn31 = >>>

Re: Commits 02795b21e753bdd4eddd7e9ebee9f50315bc0e24 and 3681fd8489cd59d0c5bc49ef38725b655d524301

Am 2016-12-16 um 18:41 schrieb Christian Schulte: Am 12/15/16 um 22:49 schrieb Michael Osipov: I would expect a VALIDATION_LEVEL_MAVEN_3_4 with VALIDATION_LEVEL_STRICT = VALIDATION_LEVEL_MAVEN_3_1. All spots which say Severity errOn31 = getSeverity( request,

Re: maven-wagon git commit: [MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management.

Am 12/16/16 um 20:30 schrieb Robert Scholte: > On Fri, 16 Dec 2016 17:25:16 +0100, Christian Schulte > wrote: > >> Am 12/16/16 um 15:21 schrieb Robert Scholte: >>> >>> but this cover the issue we are talking about, because IIUC you are >>> saying >>> that IF both junit and

Re: maven-wagon git commit: [MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management.

On Fri, 16 Dec 2016 17:25:16 +0100, Christian Schulte wrote: Am 12/16/16 um 15:21 schrieb Robert Scholte: but this cover the issue we are talking about, because IIUC you are saying that IF both junit and hamcrest get the test-scope AND hamcrest would have a dependency

Re: Commits 02795b21e753bdd4eddd7e9ebee9f50315bc0e24 and 3681fd8489cd59d0c5bc49ef38725b655d524301

First commit is not relevant to the increase of the validation level, BTW. Just the second one. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: Commits 02795b21e753bdd4eddd7e9ebee9f50315bc0e24 and 3681fd8489cd59d0c5bc49ef38725b655d524301

Am 12/15/16 um 22:49 schrieb Michael Osipov: > I would expect a VALIDATION_LEVEL_MAVEN_3_4 with VALIDATION_LEVEL_STRICT > = VALIDATION_LEVEL_MAVEN_3_1. All spots which say Severity errOn31 = > getSeverity( request, ModelBuildingRequest.VALIDATION_LEVEL_MAVEN_3_1 ); > must be turned into

Re: maven-wagon git commit: [MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management.

Am 12/16/16 um 17:25 schrieb Christian Schulte: > Am 12/16/16 um 15:21 schrieb Robert Scholte: >> >> but this cover the issue we are talking about, because IIUC you are saying >> that IF both junit and hamcrest get the test-scope AND hamcrest would have >> a dependency THEN that dependency is

Re: maven-wagon git commit: [MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management.

Am 12/16/16 um 15:21 schrieb Robert Scholte: > > but this cover the issue we are talking about, because IIUC you are saying > that IF both junit and hamcrest get the test-scope AND hamcrest would have > a dependency THEN that dependency is not added to the classpath. That is > still

[ANN] Apache Maven Dependency Plugin 3.0.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin, version 3.0.0 The dependency plugin provides the capability to manipulate artifacts. It can copy and/or unpack artifacts from local or remote repositories to a specified location.

Re: maven-wagon git commit: [MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management.

On Thu, 15 Dec 2016 23:39:50 +0100, Christian Schulte wrote: Am 12/15/16 um 23:28 schrieb Christian Schulte: different thing. Think about the dependency management as a global override of everything. That's how the resolver works. That's my Maven does it that way since

[RESULT] [VOTE] Release Apache Maven Dependency Plugin version 3.0.0

Hi, The vote has passed with the following result: +1 : Anders Hammar, Hervé BOUTEMY, Olivier Lamy, Robert Scholte PMC quorum: reached I will promote the artifacts to the central repo. On Mon, 12 Dec 2016 23:20:56 +0100, Robert Scholte wrote: Hi, We solved 25

Re: [VOTE] Release Apache Maven Dependency Plugin version 3.0.0

+1 On Mon, 12 Dec 2016 23:20:56 +0100, Robert Scholte wrote: Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12330458=Text There are still a couple of issues left in JIRA: