[jira] [Commented] (MNG-6083) Maven 3.3.9 breaks release:perform by not including maven.config
[
https://issues.apache.org/jira/browse/MNG-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453071#comment-15453071
]
Karl Heinz Marbaise commented on MNG-6083:
--
The {{.mvn/maven.config}} is only intended for Mavens command line
configuration and for nothing else and should be checked in. If this file
contains environment specific values it does not make sense. From the design
this file should not contain environment specific things. And of course if you
don't check it in into the version control the maven-release-plugin is not able
to check it out into the {{target/checkout}}.
> Maven 3.3.9 breaks release:perform by not including maven.config
>
>
> Key: MNG-6083
> URL: https://issues.apache.org/jira/browse/MNG-6083
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.3.9
>Reporter: Robert Patrick
>Priority: Blocker
>
> Our release process runs both our build and our integration tests. The
> integration tests rely on our project root directory's .mvn/maven.config file
> to run properly. The maven.config file is NOT checked into the source tree
> because it contains environment-specific values so each developer has their
> own version of it on each machine on which they build.
> This has been working fine for months now but simply changing the version of
> Maven used from 3.3.3 to 3.3.9 causes the build to break due to not having
> the -Ds defined in $PROJECT_ROOT/.mvn/maven.config.
> It appears that the release:perform goal checks out the release source in
> another location and with Maven 3.3.9, the maven.config from the original
> location is not being used. The build specifies the release-plugin version
> so the difference seems to be in the core Maven distribution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MSOURCES-104) Version 3.0.1 results in build failures
[
https://issues.apache.org/jira/browse/MSOURCES-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Corey Schooler closed MSOURCES-104.
---
Resolution: Not A Problem
> Version 3.0.1 results in build failures
> ---
>
> Key: MSOURCES-104
> URL: https://issues.apache.org/jira/browse/MSOURCES-104
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Corey Schooler
>
> When updating the pom to support plexus-archiver 3.2, a transitive dependency
> on commons-io 2.5 was introduced. Starting [after commit 1742763 |
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-source-plugin/pom.xml?view=markup&pathrev=1742763]
> when building maven-source-plugin, maven started logging the below
> {{WARNING}}.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
> (enforce-bytecode-version) on project maven-source-plugin: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
> (enforce-bytecode-version) on project maven-source-plugin: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:209)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> {code}
> It seems that commons-io 2.5 was built with a JDK not supported by the
> enforcer plugin's restrictions. This results in the following error messages
> when I build local projects:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork (default) on
> project user-roster-config: Execution default of goal
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork failed: A
> required class was missing while executing
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork:
> org/apache/commons/io/output/DeferredFileOutputStream
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSOURCES-104) Version 3.0.1 results in build failures
[
https://issues.apache.org/jira/browse/MSOURCES-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453044#comment-15453044
]
Corey Schooler commented on MSOURCES-104:
-
I'm going to close this. It seems that my local repo somehow got an unofficial
build of commons-io. Clearing my local repo resolved the issue.
> Version 3.0.1 results in build failures
> ---
>
> Key: MSOURCES-104
> URL: https://issues.apache.org/jira/browse/MSOURCES-104
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Corey Schooler
>
> When updating the pom to support plexus-archiver 3.2, a transitive dependency
> on commons-io 2.5 was introduced. Starting [after commit 1742763 |
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-source-plugin/pom.xml?view=markup&pathrev=1742763]
> when building maven-source-plugin, maven started logging the below
> {{WARNING}}.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
> (enforce-bytecode-version) on project maven-source-plugin: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
> (enforce-bytecode-version) on project maven-source-plugin: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:209)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> {code}
> It seems that commons-io 2.5 was built with a JDK not supported by the
> enforcer plugin's restrictions. This results in the following error messages
> when I build local projects:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork (default) on
> project user-roster-config: Execution default of goal
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork failed: A
> required class was missing while executing
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork:
> org/apache/commons/io/output/DeferredFileOutputStream
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MSOURCES-104) Version 3.0.1 results in build failures
[
https://issues.apache.org/jira/browse/MSOURCES-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453005#comment-15453005
]
Karl Heinz Marbaise edited comment on MSOURCES-104 at 8/31/16 6:40 PM:
---
What do you mean by {{updating the pom to support plexus-archiver 3.2}} ? Maven
Source Plugin contains plexus-archiver version 3.4? Furthermore which version
of byte-code version are you checking against via Maven Enforcer Plugin ? You
have read the announcement mail which contains an important hint about minimum
JDK 6 and Maven 3+ ?
was (Author: khmarbaise):
What do you mean by {{updating the pom to support plexus-archiver 3.2}} ? Maven
Source Plugin contains plexus-archiver version 3.4? Furthermore which version
of byte-code version are you checking against via Maven Enforcer Plugin ?
> Version 3.0.1 results in build failures
> ---
>
> Key: MSOURCES-104
> URL: https://issues.apache.org/jira/browse/MSOURCES-104
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Corey Schooler
>
> When updating the pom to support plexus-archiver 3.2, a transitive dependency
> on commons-io 2.5 was introduced. Starting [after commit 1742763 |
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-source-plugin/pom.xml?view=markup&pathrev=1742763]
> when building maven-source-plugin, maven started logging the below
> {{WARNING}}.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
> (enforce-bytecode-version) on project maven-source-plugin: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
> (enforce-bytecode-version) on project maven-source-plugin: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:209)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> {code}
> It seems that commons-io 2.5 was built with a JDK not supported by the
> enforcer plugin's restrictions. This results in the following error messages
> when I build local projects:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork (default) on
> project user-roster-config: Execution default of goal
> org.apache.maven.
[jira] [Commented] (MSOURCES-104) Version 3.0.1 results in build failures
[
https://issues.apache.org/jira/browse/MSOURCES-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453005#comment-15453005
]
Karl Heinz Marbaise commented on MSOURCES-104:
--
What do you mean by {{updating the pom to support plexus-archiver 3.2}} ? Maven
Source Plugin contains plexus-archiver version 3.4? Furthermore which version
of byte-code version are you checking against via Maven Enforcer Plugin ?
> Version 3.0.1 results in build failures
> ---
>
> Key: MSOURCES-104
> URL: https://issues.apache.org/jira/browse/MSOURCES-104
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Corey Schooler
>
> When updating the pom to support plexus-archiver 3.2, a transitive dependency
> on commons-io 2.5 was introduced. Starting [after commit 1742763 |
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-source-plugin/pom.xml?view=markup&pathrev=1742763]
> when building maven-source-plugin, maven started logging the below
> {{WARNING}}.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
> (enforce-bytecode-version) on project maven-source-plugin: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
> (enforce-bytecode-version) on project maven-source-plugin: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:209)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> {code}
> It seems that commons-io 2.5 was built with a JDK not supported by the
> enforcer plugin's restrictions. This results in the following error messages
> when I build local projects:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork (default) on
> project user-roster-config: Execution default of goal
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork failed: A
> required class was missing while executing
> org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork:
> org/apache/commons/io/output/DeferredFileOutputStream
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MCOMPILER-276) Support for the compiler option annotationpath when compilerId = eclipse
[ https://issues.apache.org/jira/browse/MCOMPILER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clóvis updated MCOMPILER-276: - Description: It is impossible to set the annotationpath with the maven compiler plugin. The option annotationpath is used to "define the locations where to find external annotations to support annotation-based null analysis". (http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_batch_compiler.htm) See also https://issues.apache.org/jira/browse/MCOMPILER-123 was: It is impossible to set the annotationpath with the maven compiler plugin. The option annotationpath is used to "define the locations where to find external annotations to support annotation-based null analysis". http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_batch_compiler.htm See also https://issues.apache.org/jira/browse/MCOMPILER-123 > Support for the compiler option annotationpath when compilerId = eclipse > > > Key: MCOMPILER-276 > URL: https://issues.apache.org/jira/browse/MCOMPILER-276 > Project: Maven Compiler Plugin > Issue Type: New Feature >Affects Versions: 3.5.1 >Reporter: Clóvis > > It is impossible to set the annotationpath with the maven compiler plugin. > The option annotationpath is used to "define the locations where to find > external annotations to support annotation-based null analysis". > (http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_batch_compiler.htm) > See also https://issues.apache.org/jira/browse/MCOMPILER-123 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MCOMPILER-276) Support for the compiler option annotationpath when compilerId = eclipse
Clóvis created MCOMPILER-276: Summary: Support for the compiler option annotationpath when compilerId = eclipse Key: MCOMPILER-276 URL: https://issues.apache.org/jira/browse/MCOMPILER-276 Project: Maven Compiler Plugin Issue Type: New Feature Affects Versions: 3.5.1 Reporter: Clóvis It is impossible to set the annotationpath with the maven compiler plugin. The option annotationpath is used to "define the locations where to find external annotations to support annotation-based null analysis". http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_batch_compiler.htm See also https://issues.apache.org/jira/browse/MCOMPILER-123 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1245) Unable to run TestNG tests using maven surefire plugin.
[
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452484#comment-15452484
]
Hemanth commented on SUREFIRE-1245:
---
I just wanted to tell you that the same project works fine in windows. Only
in mac there is an issue.
> Unable to run TestNG tests using maven surefire plugin.
> ---
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Hemanth
>Assignee: Tibor Digana
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine
> but suddenly stops working and gives me unreachable browser exception. The
> same tests finishes off its execution using failsafe plugin like a charm, but
> my reporting tool is kind of dependent on the surefire plugin. Running it by
> testng.xml(Right clicking and clicking on run as testng suite is working fine
> as well). If there is any mistake that I have done in the pom.xml please help
> me out as well. Please look into this issue.
> Here is a testng.xml
>
> http://testng.org/testng-1.0.dtd";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Here is my pom.xml
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
>
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
>
> 1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
> 1.7.7
>
> ETNA
> New standard ecommerce template
>
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>
>
>
> com.pojosontheweb
> monte-repack
> 1.0
>
>
> org.testng
> testng
> 6.9.10
> test
>
>
>
>
> com.jayway.restassured
> rest-assured
> 2.9.0
>
>
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
>
>
>
>
> org.apache.poi
> poi
> 3.13
>
>
>
> org.apache.poi
> poi-ooxml
> 3.13
>
>
> org.apache.poi
> poi-ooxml-schemas
> 3.13
>
>
>
> org.zeroturnaround
> zt-zip
> 1.7
>
>
>
> javax.mail
> mail
> 1.4.7
>
>
>
>
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
>
>
>
> org.seleniumhq.selenium
> selenium-server
> ${version.selenium}
>
>
>
>
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
>
>
> junit
> junit
>
>
>
>
>
> org.hamcrest
> hamcrest-all
> 1.3
>
>
>
> com.google.code.gson
> gson
> 2.3.1
>
>
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
>
>
>
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
>
>
>
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
>
>
>
> org.slf4j
> jcl-over-slf4j
> ${version.slf4j}
> test
>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.1
>
> ${compiler.version}
> ${compiler.version}
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.19.1
>
>
>testng.xml
>
>
>
> -javaagent:${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar
>
>
>
>
> org.aspectj
> aspectjweaver
> ${aspectj.version}
>
[jira] [Created] (MSOURCES-104) Version 3.0.1 results in build failures
Corey Schooler created MSOURCES-104:
---
Summary: Version 3.0.1 results in build failures
Key: MSOURCES-104
URL: https://issues.apache.org/jira/browse/MSOURCES-104
Project: Maven Source Plugin
Issue Type: Bug
Affects Versions: 3.0.1
Reporter: Corey Schooler
When updating the pom to support plexus-archiver 3.2, a transitive dependency
on commons-io 2.5 was introduced. Starting [after commit 1742763 |
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-source-plugin/pom.xml?view=markup&pathrev=1742763]
when building maven-source-plugin, maven started logging the below
{{WARNING}}.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
(enforce-bytecode-version) on project maven-source-plugin: Some Enforcer rules
have failed. Look above for specific messages explaining why the rule failed.
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
(enforce-bytecode-version) on project maven-source-plugin: Some Enforcer rules
have failed. Look above for specific messages explaining why the rule failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules
have failed. Look above for specific messages explaining why the rule failed.
at
org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:209)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
{code}
It seems that commons-io 2.5 was built with a JDK not supported by the enforcer
plugin's restrictions. This results in the following error messages when I
build local projects:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork (default) on
project user-roster-config: Execution default of goal
org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork failed: A
required class was missing while executing
org.apache.maven.plugins:maven-source-plugin:3.0.1:jar-no-fork:
org/apache/commons/io/output/DeferredFileOutputStream
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452292#comment-15452292
]
Tanguy Le Meur edited comment on SUREFIRE-1263 at 8/31/16 1:50 PM:
---
Hi [~tibor17],
Using Jean-Luc repo and what you suggested, I tried to have a look:
My best guess is that the name parameter in
BlockJUnit4ClassRunnerWithParameters has been used and it's {{name = [p0]}} for
example (seen with the debugger). In place of a fully qualified name.
I forked it here (look for the {{Overriden Here}} text):
https://github.com/tanguylemeur/surefire-junit-tests/blob/master/src/main/java/org/junit/runners/parameterized/BlockJUnit4ClassRunnerWithParameters.java
With this, the name are well reported in the log.
It's really dirty of course, but that was the closest way I found to display
the right message.
(https://cdn-images-1.medium.com/max/455/1*snTXFElFuQLSFDnvZKJ6IA.png)
I don't know who is right: junit or surefire.
I noticed that changing junit is messing up some other tools like eclipse with
this change.
was (Author: tlemeur):
Hi [~tibor17],
Using Jean-Luc repo and what you suggested, I tried to have a look:
My best guess is that the name parameter in
BlockJUnit4ClassRunnerWithParameters has been used and it's {code}name =
[p0]{code} for example (seen with the debugger). In place of a fully qualified
name.
I forked it here (look for the {code}Overriden Here{code} text):
https://github.com/tanguylemeur/surefire-junit-tests/blob/master/src/main/java/org/junit/runners/parameterized/BlockJUnit4ClassRunnerWithParameters.java
With this, the name are well reported in the log.
It's really dirty of course, but that was the closest way I found to display
the right message.
(https://cdn-images-1.medium.com/max/455/1*snTXFElFuQLSFDnvZKJ6IA.png)
I don't know who is right: junit or surefire.
I noticed that changing junit is messing up some other tools like eclipse with
this change.
> No class name in log when running tests in parallel with parameterized tests
>
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log
> when the tests are run in parallel with parameterized tests.
> According to this [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in
> parallel mode:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO]
>
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
> T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJuni
[jira] [Commented] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452292#comment-15452292
]
Tanguy Le Meur commented on SUREFIRE-1263:
--
Hi [~tibor17],
Using Jean-Luc repo and what you suggested, I tried to have a look:
My best guess is that the name parameter in
BlockJUnit4ClassRunnerWithParameters has been used and it's {code}name =
[p0]{code} for example (seen with the debugger). In place of a fully qualified
name.
I forked it here (look for the {code}Overriden Here{code} text):
https://github.com/tanguylemeur/surefire-junit-tests/blob/master/src/main/java/org/junit/runners/parameterized/BlockJUnit4ClassRunnerWithParameters.java
With this, the name are well reported in the log.
It's really dirty of course, but that was the closest way I found to display
the right message.
(https://cdn-images-1.medium.com/max/455/1*snTXFElFuQLSFDnvZKJ6IA.png)
I don't know who is right: junit or surefire.
I noticed that changing junit is messing up some other tools like eclipse with
this change.
> No class name in log when running tests in parallel with parameterized tests
>
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log
> when the tests are run in parallel with parameterized tests.
> According to this [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in
> parallel mode:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO]
>
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
> T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.085 sec -
> in com.appnexus.viewability.core.surefireJunitTests.ATest
> Running com.appnexus.viewability.core.surefireJunitTests.BTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec -
> in com.appnexus.viewability.core.surefireJunitTests.BTest
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> It would be great to have the classname displayed when running tests in
> parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MCOMPILER-275) Handle separate compilation of module-info.java
[
https://issues.apache.org/jira/browse/MCOMPILER-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MCOMPILER-275:
-
Attachment: mcompiler-275.patch
{quote}
I've been working on the implementation of this in the maven-compiler-plugin,
but I'm not really pleased with the result.
The problem is that in the worst case scenario we have to work with 3 different
versions of Java:
- The Maven Runtime (set as JAVA_HOME)
- JDK for the module-info.java
- JDK for all other source files.
The example below worked because all three were set to JDK9.
But based on the source/target of 1.6 I cannot predict which JDK is used, only
that it is at least JDK6. Should the plugin switch to another JDK?
And if you want to compile with source/target 1.5 or less, you're in trouble.
There's something called toolchain, where you can specify the JavaHome per
version, but in case of maven-compiler-plugin it assumes that all java-related
plugins and execution blocks want to use the same toolchain through the whole
Maven project.
The good news is that for the maven-jdeps-plugin I improved this part in Maven
3.3.1, since this plugin only works with Java8 and above, which doesn't have to
be the same JDK to compile the sources with. Now you can simple say: I want the
toolchain for version X. This feature needs to be added to the plugin.
That said I think I will write a recipe for this. This is first of all an issue
for library writers who want to have their jar compatible with multiple Java
versions for their end users.
Result: One javac call per execution block as it was meant to be.
{quote}
attachment my work so far, if we want to start a discussion about it.
> Handle separate compilation of module-info.java
> ---
>
> Key: MCOMPILER-275
> URL: https://issues.apache.org/jira/browse/MCOMPILER-275
> Project: Maven Compiler Plugin
> Issue Type: New Feature
>Reporter: Robert Scholte
> Attachments: mcompiler-275.patch
>
>
> When you want to add a module-info.java file to your project AND want your
> code to be compatible with older java version, then you need to call
> {{javac}} twice.
> To prevent all kinds of magic for selecting the right files to compile with
> the right version of Java it is probably better to just have a separate
> folder for it, e.g. {{src/main/jigsaw}}. I'd prefer to call it 'jigsaw'
> instead of java9, so it'll still makes sense once we're at java16
> On the jigsaw mailinglist they actually expect the module-info file to be in
> the {{src/main/java}} as well. Intuition of users might indeed be to simply
> put it there and let Maven handle it. That should be possible, but it also
> depends if IDEs can handle this too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451864#comment-15451864
]
Tibor Digana edited comment on SUREFIRE-1263 at 8/31/16 10:35 AM:
--
[~jderrien]
Can you help me pls with analysis and debug the plugin while building your
project {{mvnDebug test -DforkCount=0}}?
In this configuration, {{all}}, active listener is
{{ClassesParallelRunListener}} and super class {{ConcurrentRunListener}}. Most
probably test {{description}} is handled wrong. The listeners have maybe bug
for SUREFIRE-1264.
was (Author: tibor17):
[~jderrien]
Can you help me pls with analysis and debug the plugin {{mvnDebug test
-DforkCount=0}}?
In this configuration, {{all}}, active listener is
{{ClassesParallelRunListener}} and super class {{ConcurrentRunListener}}. Most
probably test {{description}} is handled wrong. The listeners have maybe bug
for SUREFIRE-1264.
> No class name in log when running tests in parallel with parameterized tests
>
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log
> when the tests are run in parallel with parameterized tests.
> According to this [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in
> parallel mode:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO]
>
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
> T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.085 sec -
> in com.appnexus.viewability.core.surefireJunitTests.ATest
> Running com.appnexus.viewability.core.surefireJunitTests.BTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec -
> in com.appnexus.viewability.core.surefireJunitTests.BTest
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> It would be great to have the classname displayed when running tests in
> parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451864#comment-15451864
]
Tibor Digana edited comment on SUREFIRE-1263 at 8/31/16 10:34 AM:
--
[~jderrien]
Can you help me pls with analysis and debug the plugin {{mvnDebug test
-DforkCount=0}}?
In this configuration, {{all}}, active listener is
{{ClassesParallelRunListener}} and super class {{ConcurrentRunListener}}. Most
probably test {{description}} is handled wrong. The listeners have maybe bug
for SUREFIRE-1264.
was (Author: tibor17):
[~jderrien]
Can you help me pls with analysis and debug the plugin {{mvnDebug test}}?
In this configuration, {{all}}, active listener is
{{ClassesParallelRunListener}} and super class {{ConcurrentRunListener}}. Most
probably test {{description}} is handled wrong. The listeners have maybe bug
for SUREFIRE-1264.
> No class name in log when running tests in parallel with parameterized tests
>
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log
> when the tests are run in parallel with parameterized tests.
> According to this [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in
> parallel mode:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO]
>
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
> T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.085 sec -
> in com.appnexus.viewability.core.surefireJunitTests.ATest
> Running com.appnexus.viewability.core.surefireJunitTests.BTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec -
> in com.appnexus.viewability.core.surefireJunitTests.BTest
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> It would be great to have the classname displayed when running tests in
> parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451864#comment-15451864
]
Tibor Digana commented on SUREFIRE-1263:
[~jderrien]
Can you help me pls with analysis and debug the plugin {{mvnDebug test}}?
In this configuration, {{all}}, active listener is
{{ClassesParallelRunListener}} and super class {{ConcurrentRunListener}}. Most
probably test {{description}} is handled wrong. The listeners have maybe bug
for SUREFIRE-1264.
> No class name in log when running tests in parallel with parameterized tests
>
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log
> when the tests are run in parallel with parameterized tests.
> According to this [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in
> parallel mode:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO]
>
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
> T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.085 sec -
> in com.appnexus.viewability.core.surefireJunitTests.ATest
> Running com.appnexus.viewability.core.surefireJunitTests.BTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec -
> in com.appnexus.viewability.core.surefireJunitTests.BTest
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> It would be great to have the classname displayed when running tests in
> parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1263:
--
Assignee: Tibor Digana
> No class name in log when running tests in parallel with parameterized tests
>
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log
> when the tests are run in parallel with parameterized tests.
> According to this [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in
> parallel mode:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO]
>
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
> T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.085 sec -
> in com.appnexus.viewability.core.surefireJunitTests.ATest
> Running com.appnexus.viewability.core.surefireJunitTests.BTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec -
> in com.appnexus.viewability.core.surefireJunitTests.BTest
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> It would be great to have the classname displayed when running tests in
> parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SUREFIRE-1264) Some tests can be lost when running in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1264:
--
Assignee: Tibor Digana
> Some tests can be lost when running in parallel with parameterized tests
>
>
> Key: SUREFIRE-1264
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1264
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
> Environment: Maven 3.3.9
> Java 1.8.0_45 (Oracle)
> System: OS X
> Reproduced on Linux too, with both OpenJDK 7 and Java 7 from Oracle.
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>
> Hello,
> It appears some tests can be lost when using the parallel mode with
> parameterized tests. Here is a [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1] I've
> used to try to reproduce the issue we have seen.
> This is not something that happens on every run, but it's quite frequent.
> With this loop, the problem should appear in less than 2 minutes, maybe on
> the first run when (un)lucky:
> {code}
> time while true; do mvn clean test > last.log ; tail -25 last.log ; if [
> "$(grep -c 'Tests run: 12' last.log)" == "0" ]; then break; fi ; done
> {code}
> Normal run:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> When tests have been lost (here one test lost according to the output):
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec -
> in [p2]
> Results :
> Tests run: 11, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> Note: there are 3 test classes and 18 tests on the [master
> branch|https://github.com/jderrien/surefire-junit-tests/tree/master] and it's
> even more frequent/easy to reproduce.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1245) Unable to run TestNG tests using maven surefire plugin.
[
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451703#comment-15451703
]
Tibor Digana commented on SUREFIRE-1245:
[~hemanth.BS]
You mean project [1]?
I did clone of Etna in May 21st and AFAIK the build was successful.
[1] https://bitbucket.org/hemanthsridhar/etna
I remember your {{testng.xml}}.
I think we should start again. What should I do?
> Unable to run TestNG tests using maven surefire plugin.
> ---
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Hemanth
>Assignee: Tibor Digana
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine
> but suddenly stops working and gives me unreachable browser exception. The
> same tests finishes off its execution using failsafe plugin like a charm, but
> my reporting tool is kind of dependent on the surefire plugin. Running it by
> testng.xml(Right clicking and clicking on run as testng suite is working fine
> as well). If there is any mistake that I have done in the pom.xml please help
> me out as well. Please look into this issue.
> Here is a testng.xml
>
> http://testng.org/testng-1.0.dtd";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Here is my pom.xml
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
>
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
>
> 1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
> 1.7.7
>
> ETNA
> New standard ecommerce template
>
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>
>
>
> com.pojosontheweb
> monte-repack
> 1.0
>
>
> org.testng
> testng
> 6.9.10
> test
>
>
>
>
> com.jayway.restassured
> rest-assured
> 2.9.0
>
>
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
>
>
>
>
> org.apache.poi
> poi
> 3.13
>
>
>
> org.apache.poi
> poi-ooxml
> 3.13
>
>
> org.apache.poi
> poi-ooxml-schemas
> 3.13
>
>
>
> org.zeroturnaround
> zt-zip
> 1.7
>
>
>
> javax.mail
> mail
> 1.4.7
>
>
>
>
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
>
>
>
> org.seleniumhq.selenium
> selenium-server
> ${version.selenium}
>
>
>
>
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
>
>
> junit
> junit
>
>
>
>
>
> org.hamcrest
> hamcrest-all
> 1.3
>
>
>
> com.google.code.gson
> gson
> 2.3.1
>
>
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
>
>
>
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
>
>
>
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
>
>
>
> org.slf4j
> jcl-over-slf4j
> ${version.slf4j}
> test
>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.1
>
> ${compiler.version}
> ${compiler.version}
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.19.1
>
>
>testng.xml
>
>
>
> -javaagent:${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar
>
>
>
>
>
