Re: Maven 3.4.0 Release

Why do you say Dependency A is transitive? Maven plugin directly depends on Dependency A, so I expect it to be present on the plugin classpath. This is consistent with how project direct optional dependencies are always present on classpath. Note that the project does not *depend* on the plugin.

[GitHub] maven-plugins pull request #98: Correct jira.codehaus.org to issues.apache.o...

Github user asfgit closed the pull request at: https://github.com/apache/maven-plugins/pull/98 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: Maven 3.4.0 Release

Corrected IT in this commit. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: Maven 3.4.0 Release

Am 12/10/16 um 13:39 schrieb Hervé BOUTEMY: > I just tested the patch associated to MNG-6110 - Upgrade Aether to Maven > Resolver 1.2, and it caused one failure in ITs > testit(org.apache.maven.it.MavenITmng4721OptionalPluginDependencyTest) Time > elapsed: 0.185 sec <<< FAILURE! >

[GitHub] maven pull request #95: [MNG-6110] updated Aether to Maven Resolver 1.2.0-SN...

Github user asfgit closed the pull request at: https://github.com/apache/maven/pull/95 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Include scope (Re: [4/4] maven git commit: [MNG-5971] Imported dependencies should be available to inheritance processing)

This commit introduces the 'include' scope - aka fixes the import scope without breaking backwards compatibility. As I am getting tired of discussing the same issue over and over again, in case there are objections, just set the 'DEPENDENCY_MANAGEMENT_IMPORT_INHERITANCE_PROCESSING' constant in

[SUREFIRE] Bring more order in the integration tests project?

Hello, at the moment the integration test project has a directory containing almost all integration tests. The Jira issue related tests are located in a sub package. The test/resources directory contains all the test projects with no further ordering. This makes it hard to navigate through the

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

On Sat, 10 Dec 2016 18:59:50 +0100, Christian Schulte wrote: Am 12/10/16 um 18:54 schrieb Robert Scholte: Done as well Thanks. Does that mean I need to re-generate the website or does this just affect the announcement mail? If you are talking about the date on the

Re: [ANN] Apache Maven Resources Plugin 3.0.2 Released

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

[ANN] Apache Maven Resources Plugin 3.0.2 Released

The Maven team is pleased to announce the release of the Apache Maven Resources Plugin, version 3.0.2 The Resources Plugin handles the copying of project resources to the output directory. There are two different kinds of resources: main resources and test resources. The difference is

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Am 12/10/16 um 18:54 schrieb Robert Scholte: > Done as well Thanks. Does that mean I need to re-generate the website or does this just affect the announcement mail? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Done as well Robert On Sat, 10 Dec 2016 18:47:00 +0100, Christian Schulte wrote: Am 12/10/16 um 18:28 schrieb Robert Scholte: Done One more step I cannot perform myself: 3. Update the version tracking in JIRA In the relevant project, go to Administration, then

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Am 12/10/16 um 18:28 schrieb Robert Scholte: > Done One more step I cannot perform myself: 3. Update the version tracking in JIRA In the relevant project, go to Administration, then Versions. Mark the Y.Z version as 'released'. Create version Y.Z+1, if that hasn't already been done. You may

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Am 12/10/16 um 18:28 schrieb Robert Scholte: > Done Thanks! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven 3.4.0 Release

Am 12/10/16 um 17:48 schrieb Michael Osipov: > Can you create a proper branch with fixed ITs? I'd like to run those. > From my point of view, we can release Resolver 1.2 and roll an RC for > Maven 3.4. Let's just switch maven master to the resolver snapshot and continue from there on. That

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Done On Sat, 10 Dec 2016 18:25:20 +0100, Christian Schulte wrote: Am 12/10/16 um 16:48 schrieb Robert Scholte: Hi Christian, See http://maven.apache.org/developers/release/maven-project-release-procedure.html#Copy_the_source_release_to_the_Apache_Distribution_Area the

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Am 12/10/16 um 16:48 schrieb Robert Scholte: > Hi Christian, > > See > http://maven.apache.org/developers/release/maven-project-release-procedure.html#Copy_the_source_release_to_the_Apache_Distribution_Area > > the last sense of the first paragraph: > Currently this requires to be in

Re: Maven 3.4.0 Release

Am 2016-12-10 um 16:06 schrieb Christian Schulte: If it's happening just due to the upgrade of the resolver, then it's a resolver bugfix the IT hasn't been updated to reflect. I discussed this issue with Jason in december last year when upgrading the resolver to 1.1 needed to be reverted.

Re: Maven 3.4.0 Release

Am 2016-12-10 um 16:18 schrieb Christian Schulte: It would be cool if someone could answer the questions I raised in this thread. I would still need to remove those system properties from the 'DefaultModelBuilder', for example.

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Hi Christian, See http://maven.apache.org/developers/release/maven-project-release-procedure.html#Copy_the_source_release_to_the_Apache_Distribution_Area the last sense of the first paragraph: Currently this requires to be in maven-pmc group I'll do this for you. Robert On Sat,

Re: Maven 3.4.0 Release

Wait. That maybe a different story. MRESOLVER-8. The changes to 'OptionalDependencySelector' made it behave the same way the 'ScopeDependencySelector' and other selectors are

Re: Maven 3.4.0 Release

It would be cool if someone could answer the questions I raised in this thread. I would still need to remove those system properties from the 'DefaultModelBuilder', for example.

Re: Maven 3.4.0 Release

If it's happening just due to the upgrade of the resolver, then it's a resolver bugfix the IT hasn't been updated to reflect. I discussed this issue with Jason in december last year when upgrading the resolver to 1.1 needed to be reverted.

Re: [RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.2

Seems I do not have permission to add the source release to the dist area. Can someone else add the files for me, please? I would like to follow the release process document step by step. This is the next step I would not want to skip for later. svn: E195023: Commit failed (details follow): svn:

Re: Maven 3.4.0 Release

Am 2016-12-10 um 13:39 schrieb Hervé BOUTEMY: I just tested the patch associated to MNG-6110 - Upgrade Aether to Maven Resolver 1.2, and it caused one failure in ITs testit(org.apache.maven.it.MavenITmng4721OptionalPluginDependencyTest) Time elapsed: 0.185 sec <<< FAILURE!

Re: Maven 3.4.0 Release

I just tested the patch associated to MNG-6110 - Upgrade Aether to Maven Resolver 1.2, and it caused one failure in ITs testit(org.apache.maven.it.MavenITmng4721OptionalPluginDependencyTest) Time elapsed: 0.185 sec <<< FAILURE! junit.framework.AssertionFailedError: expected:<1> but was:<0> Is