Re: Maven enforcer 3.0.0. release (1.9 compatibility)

Just for completeness -- 3.0.0-M1 works like a charm for me with the newest Java 9. Thanks Robert. Dawid On Mon, Jul 24, 2017 at 7:11 PM, Robert Scholte wrote: > Hi Stephen, > > See the details of MENFORCER-277. Looks like there's some extra work > required first on other

[VOTE] Apache Maven Wagon 3.0.0

Hi I'd like to release Apache Maven Wagon 3.0.0. We fixed 4 issues: https://s.apache.org/WAGON-3.0.0 Staging repository: https://repository.apache.org/content/repositories/maven-1351/ Sources:

[GitHub] maven-surefire issue #155: Revert junit-plattform provider code from 3.0-rc1...

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/155 @britter #155 and #154 are done. Pls let me know if I should continue with #153. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] maven-surefire pull request #155: Revert junit-plattform provider code from ...

Github user asfgit closed the pull request at: https://github.com/apache/maven-surefire/pull/155 --- 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

[GitHub] maven-surefire issue #161: SUREFIRE-1396: Provider class path is incorrect f...

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/161 @jon-bell I will investigate this issue: `Could not find artifact org.apache.maven.surefire:it-parent:pom:1.0 in central (https://repo.maven.apache.org/maven2)` --- If your project

[GitHub] maven-surefire pull request #154: Move junit5 provider code

Github user asfgit closed the pull request at: https://github.com/apache/maven-surefire/pull/154 --- 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

maven-release-plugin and signing artifacts

Hi, I have tried to make a release of the plexus-utils and was faced with a problem...which I currently don't understand... I have started the release with: mvn -Darguments='-Dgpg.keyname=kama' release:prepare release:perform So I thought the gpg.keyname property will be given to the

[ANN] Plexus Utils 3.1.0 Released

Hi to all, we are pleased to announce the Plexus Utils Version 3.1.0 http://codehaus-plexus.github.io/plexus-utils/ The new version can be used by the following coordinates: org.codehaus.plexus plexus-utils 3.1.0 The following issues have been solved.

Re: MNG-6216 - Plexus-Utils ?

Hi, release of plexus-utils is done... Branch for this issue is created which contains the updated version of plexus-utils.. So I will integrate that fix into master on sonday..if no one has objections...assumed the IT's will work fine.. ;-).. Kind regards Karl Heinz Marbaise On

Need for code review and test of branch SUREFIRE-1400 (see Jira ticket)

Hi devs, Hi Guillaume Boué, Can you please test this branch on Maven Assembly build and make a code review? On Windows. Here we have a commit in branch SUREFIRE-1400, see [1]. The point of this fix is to start Surefire Booter JAR from ${java.io.tmpdir}/surefire-***/surefire*.jar instead of

Fwd: SUREFIRE-1262

Hello Robert, Hello devs, My proposal is to follow these steps. It might be faster to split this activity to multiple ones and solve them separately in branches in parallel but finish it in release 2.20.2, otherwise the release 2.20.1 will be quite postponed. Maybe we should split SUREFIRE-1262