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

Github user jon-bell commented on the issue: https://github.com/apache/maven-surefire/pull/161 @Tibor17 It seems like it had worked for me because I had previously executed a `mvn install` - I see on a clean maven repo the problem. It looks like the `SurefireLauncher` does

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

This is very nice Tibor! All the ITs of maven-assembly-plugin that were failing on my Windows set-up are now running fine. I tested this branch both with JDK 7 and 8 on Windows 10. I also checked that the temporary "surefire" directories located in %TEMP% were correctly deleted at the end of

Re: [VOTE] Apache Maven Wagon 3.0.0

Hi, +1 from me... I have tested with "mvn clean verify" and found a things like the following in the log files: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running

Re: [VOTE] Apache Maven Wagon 3.0.0

There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012318122%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Source release checksum(s): wagon-3.0.0-source-release.zip sha1:

Re: [ANN] First call to round up issues for 3.5.1

On Fri, 23 Jun 2017 16:27:03 +0200, Robert Scholte wrote: Looking for someone who can second the following issues: Second attempt: MNG-6148: Can't package and assemble with JDK9/Jigsaw See

Re: maven-release-plugin and signing artifacts

Hi Karl Heinz, this can happen when the plugin configuration contains a fixed value for arguments, i.e -Dkey=value If you want arguments to be extended via commandline argument, you need to do this: -Dkey=value ${arguments} Robert On Thu, 03 Aug 2017 19:57:10 +0200, Karl Heinz