[GitHub] maven-surefire issue #150: SUREFIRE-1372 Filter tests to be rerun by descrip...

2017-09-03 Thread johnktims 
Github user johnktims commented on the issue:

https://github.com/apache/maven-surefire/pull/150
  
Cucumber 2.0.0 was released a few days ago.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: [VOTE] Release Apache Maven Compiler Plugin version 3.7.0

2017-09-03 Thread Mark Derricutt 
The problems with errorprone have been fixed in the recent 2.1.1 release so
you could update the tests with that maybe?

-- 
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree

On Sat, Sep 2, 2017 at 11:30 PM, Robert Scholte 
wrote:

> Hi Karl Heinz,
>
> this is a problem with the error-prone-compiler[1], a specific
> implementation of the compiler-api and also where this must be fixed.
> You might wonder if it should be tested here, but now we are at least
> aware that current error-prone-compiler is not Java9 compatible. It should
> not be a blocker for the maven-compiler-plugin itself.
>
> thank,
> Robert
>
> [1] https://github.com/codehaus-plexus/plexus-compiler/tree/mast
> er/plexus-compilers/plexus-compiler-javac-errorprone
>
>
>
> On Sat, 02 Sep 2017 13:23:50 +0200, Karl Heinz Marbaise 
> wrote:
>
> Hi,
>>
>> I have tested the following combinations:
>>
>> jdk1.7.0_79.jdk
>>apache-maven-3.0.5
>>apache-maven-3.1.1
>>apache-maven-3.2.5
>>apache-maven-3.3.1
>>apache-maven-3.3.9
>>apache-maven-3.5.0
>> jdk1.8.0_131.jdk
>>apache-maven-3.0.5
>>apache-maven-3.1.1
>>apache-maven-3.2.5
>>apache-maven-3.3.1
>>apache-maven-3.3.9
>>apache-maven-3.5.0
>> jdk1.8.0_144.jdk
>>apache-maven-3.0.5
>>apache-maven-3.1.1
>>apache-maven-3.2.5
>>apache-maven-3.3.1
>>apache-maven-3.3.9
>>apache-maven-3.5.0
>> jdk1.9.0_ea+181.jdk
>>apache-maven-3.0.5 FAILED!!
>>apache-maven-3.1.1 FAILED!!
>>apache-maven-3.2.5 FAILED!!
>>apache-maven-3.3.1 FAILED!!
>>apache-maven-3.3.9 FAILED!!
>>apache-maven-3.5.0 FAILED!!
>>
>>
>> But the JDK1.9.0_ea+181 have show the following result (for all Maven
>> versions):
>>
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
>> (default-compile) on project error-prone-compiler: Fatal error compiling:
>> CompilerException: InvocationTargetException: 
>> java.nio.file.NotDirectoryException:
>> /Library/Java/JavaVirtualMachines/jdk1.9.0_ea+181.jdk/Contents/Home/lib/modules
>> -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed
>> to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
>> (default-compile) on project error-prone-compiler: Fatal error compiling
>> at org.apache.maven.lifecycle.int
>> ernal.MojoExecutor.execute(MojoExecutor.java:217)
>> at org.apache.maven.lifecycle.int
>> ernal.MojoExecutor.execute(MojoExecutor.java:153)
>> at org.apache.maven.lifecycle.int
>> ernal.MojoExecutor.execute(MojoExecutor.java:145)
>> at org.apache.maven.lifecycle.int
>> ernal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> at org.apache.maven.lifecycle.int
>> ernal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> at org.apache.maven.lifecycle.int
>> ernal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> at org.apache.maven.lifecycle.int
>> ernal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> at org.apache.maven.DefaultMaven.
>> doExecute(DefaultMaven.java:320)
>> at org.apache.maven.DefaultMaven.
>> execute(DefaultMaven.java:156)
>> at org.apache.maven.cli.MavenCli.
>> execute(MavenCli.java:537)
>> at org.apache.maven.cli.MavenCli.
>> doMain(MavenCli.java:196)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>> at java.base/jdk.internal.reflect
>> .NativeMethodAccessorImpl.invoke0(Native Method)
>> at java.base/jdk.internal.reflect
>> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at java.base/jdk.internal.reflect
>> .DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
>> rImpl.java:43)
>> at java.base/java.lang.reflect.Me
>> thod.invoke(Method.java:564)
>> at org.codehaus.plexus.classworld
>> s.launcher.Launcher.launchEnhanced(Launcher.java:290)
>> at org.codehaus.plexus.classworld
>> s.launcher.Launcher.launch(Launcher.java:230)
>> at org.codehaus.plexus.classworld
>> s.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>> at org.codehaus.plexus.classworld
>> s.launcher.Launcher.main(Launcher.java:352)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal
>> error compiling
>> at org.apache.maven.plugin.compil
>> er.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1086)
>> at org.apache.maven.plugin.compil
>> er.CompilerMojo.execute(CompilerMojo.java:168)
>> at org.apache.maven.plugin.Defaul
>> tBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>> at org.apache.maven.lifecycle.int
>>