[jira] [Commented] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong

[Trejkaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425770#comment-15425770
 ] 

Trejkaz commented on MCOMPILER-274:
---

Maybe this is even a bug. If I read the source:

https://maven.apache.org/plugins/maven-compiler-plugin/xref/org/apache/maven/plugin/compiler/AbstractCompilerMojo.html#L976

Suspicious things:

1) It's creating an exception just because there were warnings.

2) I don't see any of these supposed warnings in the output either.

3) It's putting strings into the exception object, when it should be putting in 
a Throwable indicating the actual problem.


> "Compilation failure" message should say what actually went wrong
> -
>
> Key: MCOMPILER-274
> URL: https://issues.apache.org/jira/browse/MCOMPILER-274
> Project: Maven Compiler Plugin
>  Issue Type: Improvement
>Affects Versions: 3.1, 3.5.1
>Reporter: Trejkaz
> Attachments: out.txt
>
>
> I tried to build jruby 9.0.5.0, which uses Maven to run the build. It fails 
> to compile, but gives me a useless error message:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project jruby-core: Compilation failure -> [Help 1]
> When compilation fails, Maven should tell me what actually went wrong, so 
> that I can fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong

[Trejkaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425761#comment-15425761
 ] 

Trejkaz commented on MCOMPILER-274:
---

Tried editing the project's POM to say 3.5.1, same result.


> "Compilation failure" message should say what actually went wrong
> -
>
> Key: MCOMPILER-274
> URL: https://issues.apache.org/jira/browse/MCOMPILER-274
> Project: Maven Compiler Plugin
>  Issue Type: Improvement
>Affects Versions: 3.1, 3.5.1
>Reporter: Trejkaz
> Attachments: out.txt
>
>
> I tried to build jruby 9.0.5.0, which uses Maven to run the build. It fails 
> to compile, but gives me a useless error message:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project jruby-core: Compilation failure -> [Help 1]
> When compilation fails, Maven should tell me what actually went wrong, so 
> that I can fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong

[Trejkaz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Trejkaz updated MCOMPILER-274:
--
Affects Version/s: (was: 3.3)
   3.5.1

> "Compilation failure" message should say what actually went wrong
> -
>
> Key: MCOMPILER-274
> URL: https://issues.apache.org/jira/browse/MCOMPILER-274
> Project: Maven Compiler Plugin
>  Issue Type: Improvement
>Affects Versions: 3.1, 3.5.1
>Reporter: Trejkaz
> Attachments: out.txt
>
>
> I tried to build jruby 9.0.5.0, which uses Maven to run the build. It fails 
> to compile, but gives me a useless error message:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project jruby-core: Compilation failure -> [Help 1]
> When compilation fails, Maven should tell me what actually went wrong, so 
> that I can fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong

[Trejkaz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Trejkaz updated MCOMPILER-274:
--
Affects Version/s: 3.1
   3.3

> "Compilation failure" message should say what actually went wrong
> -
>
> Key: MCOMPILER-274
> URL: https://issues.apache.org/jira/browse/MCOMPILER-274
> Project: Maven Compiler Plugin
>  Issue Type: Improvement
>Affects Versions: 3.1, 3.3
>Reporter: Trejkaz
> Attachments: out.txt
>
>
> I tried to build jruby 9.0.5.0, which uses Maven to run the build. It fails 
> to compile, but gives me a useless error message:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project jruby-core: Compilation failure -> [Help 1]
> When compilation fails, Maven should tell me what actually went wrong, so 
> that I can fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong

[Trejkaz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Trejkaz updated MCOMPILER-274:
--
Attachment: out.txt

Attaching full output showing that even the full logging doesn't show the 
problem either.


> "Compilation failure" message should say what actually went wrong
> -
>
> Key: MCOMPILER-274
> URL: https://issues.apache.org/jira/browse/MCOMPILER-274
> Project: Maven Compiler Plugin
>  Issue Type: Improvement
>Reporter: Trejkaz
> Attachments: out.txt
>
>
> I tried to build jruby 9.0.5.0, which uses Maven to run the build. It fails 
> to compile, but gives me a useless error message:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project jruby-core: Compilation failure -> [Help 1]
> When compilation fails, Maven should tell me what actually went wrong, so 
> that I can fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong

[Trejkaz (JIRA)]

Trejkaz created MCOMPILER-274:
-

 Summary: "Compilation failure" message should say what actually 
went wrong
 Key: MCOMPILER-274
 URL: https://issues.apache.org/jira/browse/MCOMPILER-274
 Project: Maven Compiler Plugin
  Issue Type: Improvement
Reporter: Trejkaz


I tried to build jruby 9.0.5.0, which uses Maven to run the build. It fails to 
compile, but gives me a useless error message:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project jruby-core: Compilation failure -> [Help 1]

When compilation fails, Maven should tell me what actually went wrong, so that 
I can fix it.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MNG-6081) Log refactoring - Method Invocation Replaced By Variable

[Nemo Chen (JIRA)]

Nemo Chen created MNG-6081:
--

 Summary: Log refactoring - Method Invocation Replaced By Variable
 Key: MNG-6081
 URL: https://issues.apache.org/jira/browse/MNG-6081
 Project: Maven
  Issue Type: Bug
Affects Versions: 3.3.9
Reporter: Nemo Chen


*Method Invocation Replaced By Variable*
In file: 
apache-maven-3.3.9/maven-compat/src/main/java/org/apache/maven/artifact/resolver/DebugResolutionListener.java

from line 70:
{code}
String keptVersion = kept.getVersion();

if ( omittedVersion != null ? !omittedVersion.equals( keptVersion ) : 
keptVersion != null )
{
logger.debug( indent + omitted + " (removed - nearer found: " + 
kept.getVersion() + ")" );
}
{code}

the "kept.getVersion()" can be replaced with "keptVersion" for the sake of 
simplicity and readability.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MJAVADOC-471) When aggregator filters out artifacts of current reactor projects, only the primary artifact is considered

[Matt Benson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425564#comment-15425564
 ] 

Matt Benson commented on MJAVADOC-471:
--

You might notice that given the example structure, you would expect that 
{{foo-child-2}} would depend on {{foo-child-1:tests}} only in {{test}} scope, 
and therefore that the problem reported would actually apply not to 
{{aggregate}} but instead to {{test-aggregate}}. With this in mind, my 
recommendation is that, additionally, {{AbstractJavadocMojo}} should filter 
dependencies by scope and my forthcoming patch will reflect this.

> When aggregator filters out artifacts of current reactor projects, only the 
> primary artifact is considered
> --
>
> Key: MJAVADOC-471
> URL: https://issues.apache.org/jira/browse/MJAVADOC-471
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Matt Benson
>
> given project structure
> {code}
> foo-parent
>  - foo-child-1
>  - foo-child-2
> {code}
> If {{foo-child-2}} depends on the {{tests}} artifact of {{foo-child-1}} the 
> build still breaks, despite the changes made for MJAVADOC-437 .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MJAVADOC-471) When aggregator filters out artifacts of current reactor projects, only the primary artifact is considered

[Matt Benson (JIRA)]

Matt Benson created MJAVADOC-471:


 Summary: When aggregator filters out artifacts of current reactor 
projects, only the primary artifact is considered
 Key: MJAVADOC-471
 URL: https://issues.apache.org/jira/browse/MJAVADOC-471
 Project: Maven Javadoc Plugin
  Issue Type: Bug
  Components: javadoc
Affects Versions: 2.10.4
Reporter: Matt Benson


given project structure

{code}
foo-parent
 - foo-child-1
 - foo-child-2
{code}
If {{foo-child-2}} depends on the {{tests}} artifact of {{foo-child-1}} the 
build still breaks, despite the changes made for MJAVADOC-437 .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MSHADE-203) "shadeTestJar" option not working?

[JIRA]

[ 
https://issues.apache.org/jira/browse/MSHADE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425548#comment-15425548
 ] 

Stéphane Landelle commented on MSHADE-203:
--

Building on top of William's explanations, I went with a different solution and 
recreated the whole project dependency graph with Aether (injected 
ProjectDependenciesResolver) to I could get the test dependencies back.
If there's some interest for it, I could provide a gist.


> "shadeTestJar" option not working?
> --
>
> Key: MSHADE-203
> URL: https://issues.apache.org/jira/browse/MSHADE-203
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.4.1
>Reporter: Aaron Curley
>Priority: Minor
>
> So, I'm pretty new to using the maven-shade-plugin and I'm not really that 
> familiar with the maven-shade-plugin's design/code; however, it appears that 
> the  option in the maven-shade-plugin configuration does not 
> work correctly.  
> __Symtoms__
> While running "mvn package" in my project (which has  set to 
> true), maven-shade-plugin appears to perform the "test jar shading" step 
> (after performing the regular jar's shade), but the "shaded" test JAR doesn't 
> actually include any shaded dependency files (it just includes the "original" 
> test jar's contents, which is essentially a "no-op").
> __Possible Diagnosis__
> I took a quick look at the release code base for v2.4.1, in particularly, the 
> mojo/ShadeMojo.java file.  In the execute() method, at line 437, there is 
> method call:
> processArtifactSelectors( artifacts, artifactIds, sourceArtifacts, 
> artifactSelector );
> This method call appears to populate the "artifacts" and "sourceArtifacts" 
> sets created earlier in execute() but the code noticeably does not populate 
> the similar "testArtifacts" set.  My guess is that this is causing the 
> "shade" operation to skip processing any artifacts for the test jar shade 
> operation (since only the project-level artifact is populated in the 
> "testArtifacts" set at line 432).
> __Possible Solution__
> (Obviously) Add an additional parameter to processArtifactSelectors() that 
> accepts the additional "testArtifacts" set.  Then, processArtifactSelectors 
> could populate that set (much like it does for the "sourceArtifacts" set at 
> line 623).  A more extensible design might be to populate a list of Set's and 
> supply that to processArtifactSelectors(), but there are some other 
> difficulties with that (under the current design).
> Best wishes.  Like I said, I'm pretty new to this plugin, so the above may be 
> incorrect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-5909) Activating a profile based on the existence of multiple files is not possible

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425449#comment-15425449
 ] 

ASF GitHub Bot commented on MNG-5909:
-

GitHub user lbndev opened a pull request:

https://github.com/apache/maven/pull/92

MNG-5909 : Add combined expression evaluator to file activation property

Suggested solution for MNG-5909 : the file activation element will 
understand basic boolean expressions such as and(file1,file2) or(file3,!file4) 
etc... Please see added unit test for expression examples.
If you think this could benefit to other activators (property, os, ...) 
please say so and I will happily modify them too.
I will also post a message on maven dev mailing list.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lbndev/maven MNG-5909

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/92.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #92


commit 2efe3d2d3b92685d83c2598a7f85c39ebdd59ebc
Author: Loïc B 
Date:   2016-08-16T09:21:52Z

Add combined expression evaluator to file activation property




> Activating a profile based on the existence of multiple files is not possible
> -
>
> Key: MNG-5909
> URL: https://issues.apache.org/jira/browse/MNG-5909
> Project: Maven
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 3.3.3
>Reporter: Konrad Windszus
>
> Currently each type of activation (os, jdk, file, property) can only be used 
> once for activating a single profile.
> Therefore it is not possible to activate a profile in case two different 
> files are existing, although since Maven 3.2.2 (MNG-4565) it is possible to 
> combine multiple activations of different types.
> Multiple  {{file}} or {{property}} should therefore be supported to allow to 
> express something like:
> Enable {{profileA}} in case both {{fileA}} and {{fileB}} do exists
> For {{jdk}} and {{os}} this is less relevant because all conditions are 
> combined with AND.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SUREFIRE-1269) FileNotFoundException by SureFire after execution of tests

[Tibor Digana (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana closed SUREFIRE-1269.
--
Resolution: Not A Bug

[~dkm87]
IIUC it's related to TestNG and Surefire can close this.
Feel free to let me know if I should reopen it.

> FileNotFoundException by SureFire after execution of tests
> --
>
> Key: SUREFIRE-1269
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1269
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin, TestNG support
>Affects Versions: 2.19.1
> Environment: OS: Win10
> Java: 8 rev.102
> Maven: 3.3.9
> TestNG: 6.9.10
> SureFire: 2.19.1
> SystemMemory: 16G
>Reporter: Deepak Mahapatro
>Assignee: Tibor Digana
>Priority: Minor
> Attachments: Test.zip, screenshot-1.png
>
>
> After executing tests, maven is throwing a FienotFoundException which 
> originates from surefire (I understood the source from trace.). 
> java.io.FileNotFoundException: \Users\cedric\java\misc\jquery\head (The 
> system cannot find the path specified)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at org.testng.reporters.Files.readFile(Files.java:21)
> at org.testng.reporters.JqReporter.generateReport(JqReporter.java:40)
> at org.testng.TestNG.generateReports(TestNG.java:1135)
> at org.testng.TestNG.run(TestNG.java:1081)
> at 
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:281)
> at 
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75)
> at 
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:121)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> This is not impacting either test result or build status but it is creating 
> some confusion while analyzing logs from both file system and from maven 
> console.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SUREFIRE-1269) FileNotFoundException by SureFire after execution of tests

[Tibor Digana (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana reassigned SUREFIRE-1269:
--

Assignee: Tibor Digana

> FileNotFoundException by SureFire after execution of tests
> --
>
> Key: SUREFIRE-1269
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1269
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin, TestNG support
>Affects Versions: 2.19.1
> Environment: OS: Win10
> Java: 8 rev.102
> Maven: 3.3.9
> TestNG: 6.9.10
> SureFire: 2.19.1
> SystemMemory: 16G
>Reporter: Deepak Mahapatro
>Assignee: Tibor Digana
>Priority: Minor
> Attachments: Test.zip, screenshot-1.png
>
>
> After executing tests, maven is throwing a FienotFoundException which 
> originates from surefire (I understood the source from trace.). 
> java.io.FileNotFoundException: \Users\cedric\java\misc\jquery\head (The 
> system cannot find the path specified)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at org.testng.reporters.Files.readFile(Files.java:21)
> at org.testng.reporters.JqReporter.generateReport(JqReporter.java:40)
> at org.testng.TestNG.generateReports(TestNG.java:1135)
> at org.testng.TestNG.run(TestNG.java:1081)
> at 
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:281)
> at 
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75)
> at 
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:121)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> This is not impacting either test result or build status but it is creating 
> some confusion while analyzing logs from both file system and from maven 
> console.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6024) maven-antrun-plugin:instrument failing NoClassDefFoundError: org/slf4j/LoggerFactory

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425265#comment-15425265
 ] 

Michael Osipov commented on MNG-6024:
-

I can confirm this.

Dependency tree before:
{noformat}
[DEBUG] org.apache.maven.plugins:maven-antrun-plugin:jar:1.8:
[DEBUG]net.sourceforge.cobertura:cobertura:jar:2.1.1:runtime
[DEBUG]   org.ow2.asm:asm:jar:5.0.1:runtime
[DEBUG]   org.ow2.asm:asm-tree:jar:5.0.1:runtime
[DEBUG]   org.ow2.asm:asm-commons:jar:5.0.1:runtime
[DEBUG]   org.ow2.asm:asm-util:jar:5.0.1:runtime
[DEBUG]   org.ow2.asm:asm-analysis:jar:5.0.1:runtime
[DEBUG]   oro:oro:jar:2.0.8:runtime
[DEBUG]   jaxen:jaxen:jar:1.1.4:runtime
[DEBUG]   org.apache.ant:ant-junit:jar:1.8.3:runtime
[DEBUG]   org.mortbay.jetty:servlet-api-2.5:jar:6.1.14:runtime
[DEBUG]   org.mortbay.jetty:jetty:jar:6.1.14:runtime
[DEBUG]   org.mortbay.jetty:jetty-util:jar:6.1.14:runtime
[DEBUG]   com.sun:tools:jar:0:system
[DEBUG]   org.slf4j:slf4j-api:jar:1.7.5:runtime
[DEBUG]   ch.qos.logback:logback-classic:jar:1.0.13:runtime
[DEBUG]  ch.qos.logback:logback-core:jar:1.0.13:runtime
[DEBUG]   junit:junit:jar:4.11:compile
[DEBUG]  org.hamcrest:hamcrest-core:jar:1.3:compile
[DEBUG]   org.apache.commons:commons-lang3:jar:3.3.2:runtime
[DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile
[DEBUG]org.apache.maven:maven-project:jar:2.2.1:compile
[DEBUG]   org.apache.maven:maven-settings:jar:2.2.1:compile
[DEBUG]   org.apache.maven:maven-profile:jar:2.2.1:compile
[DEBUG]   org.apache.maven:maven-model:jar:2.2.1:compile
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.2.1:compile
[DEBUG]  org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
[DEBUG]  
backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
[DEBUG]   org.apache.maven:maven-plugin-registry:jar:2.2.1:compile
[DEBUG]   org.codehaus.plexus:plexus-interpolation:jar:1.11:compile
[DEBUG]   
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG]  classworlds:classworlds:jar:1.1-alpha-2:compile
[DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
[DEBUG]org.codehaus.plexus:plexus-utils:jar:3.0.20:compile
[DEBUG]org.apache.ant:ant:jar:1.9.4:compile
[DEBUG]   org.apache.ant:ant-launcher:jar:1.9.4:compile
{noformat}

and after population

{noformat}
[DEBUG] Importing foreign packages into class realm 
plugin>org.apache.maven.plugins:maven-antrun-plugin:1.8
[DEBUG]   Imported:  < maven.api
[DEBUG] Populating class realm 
plugin>org.apache.maven.plugins:maven-antrun-plugin:1.8
[DEBUG]   Included: org.apache.maven.plugins:maven-antrun-plugin:jar:1.8
[DEBUG]   Included: net.sourceforge.cobertura:cobertura:jar:2.1.1
[DEBUG]   Included: org.ow2.asm:asm:jar:5.0.1
[DEBUG]   Included: org.ow2.asm:asm-tree:jar:5.0.1
[DEBUG]   Included: org.ow2.asm:asm-commons:jar:5.0.1
[DEBUG]   Included: org.ow2.asm:asm-util:jar:5.0.1
[DEBUG]   Included: org.ow2.asm:asm-analysis:jar:5.0.1
[DEBUG]   Included: oro:oro:jar:2.0.8
[DEBUG]   Included: jaxen:jaxen:jar:1.1.4
[DEBUG]   Included: org.apache.ant:ant-junit:jar:1.8.3
[DEBUG]   Included: org.mortbay.jetty:servlet-api-2.5:jar:6.1.14
[DEBUG]   Included: org.mortbay.jetty:jetty:jar:6.1.14
[DEBUG]   Included: org.mortbay.jetty:jetty-util:jar:6.1.14
[DEBUG]   Included: com.sun:tools:jar:0
[DEBUG]   Included: ch.qos.logback:logback-classic:jar:1.0.13
[DEBUG]   Included: ch.qos.logback:logback-core:jar:1.0.13
[DEBUG]   Included: junit:junit:jar:4.11
[DEBUG]   Included: org.hamcrest:hamcrest-core:jar:1.3
[DEBUG]   Included: org.apache.commons:commons-lang3:jar:3.3.2
[DEBUG]   Included: backport-util-concurrent:backport-util-concurrent:jar:3.1
[DEBUG]   Included: org.codehaus.plexus:plexus-interpolation:jar:1.11
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:3.0.20
[DEBUG]   Included: org.apache.ant:ant:jar:1.9.4
[DEBUG]   Included: org.apache.ant:ant-launcher:jar:1.9.4
[DEBUG] Configuring mojo org.apache.maven.plugins:maven-antrun-plugin:1.8:run 
from plugin realm 
ClassRealm[plugin>org.apache.maven.plugins:maven-antrun-plugin:1.8, parent: 
sun.misc.Launcher$AppClassLoader@5c647e05]
{noformat}

> maven-antrun-plugin:instrument failing NoClassDefFoundError: 
> org/slf4j/LoggerFactory
> 
>
> Key: MNG-6024
> URL: https://issues.apache.org/jira/browse/MNG-6024
> Project: Maven
>  Issue Type: Bug
>  Components: Class Loading
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
> Environment: Window 7, JDK 1.8.0_40
>Reporter: S V Mohana Rao
>Priority: Blocker
> Attachments: maven-core-slf4j-issue.zip, mvn-coreslf4j-issue.txt
>
>
> Related issues : MNG-5783, MNG-5817. I was using 

[jira] [Closed] (MNG-6031) Moving from Maven 3.2.5 or older to Maven 3.3.1 or newer breaks maven-antrun-plugin

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6031.
---
Resolution: Duplicate

> Moving from Maven 3.2.5 or older to Maven 3.3.1 or newer breaks 
> maven-antrun-plugin
> ---
>
> Key: MNG-6031
> URL: https://issues.apache.org/jira/browse/MNG-6031
> Project: Maven
>  Issue Type: Bug
>  Components: Class Loading, core
>Affects Versions: 3.3.3, 3.3.9
> Environment: Windows 7, JDK 1.8.0_51
>Reporter: Andrei Serea
>Priority: Blocker
> Attachments: pom.xml
>
>
> Running with maven-antrun-plugin an ant target that requires SLF4J breaks 
> with a NoClassDefFoundError.
> The example attached calls the cobertura-merge ant task and the error is:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/slf4j/LoggerFactory
> {code}
> [INFO] Scanning for projects...
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building Cobertura Merge test 1.12-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cobertura-report ---
> [INFO] Deleting C:\IBXProjects\SUE\git\discovery\src\java\cobertura\target
> [INFO] 
> [INFO] --- maven-antrun-plugin:1.8:run (cobertura-merge-base) @ 
> cobertura-report ---
> [INFO] Executing tasks
> main:
> [cobertura-merge] Cobertura 2.1.1 - GNU GPL License (NO WARRANTY) - See 
> COPYRIGHT file
> [cobertura-merge] Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/slf4j/LoggerFactory
> [cobertura-merge] at 
> net.sourceforge.cobertura.util.CommandLineBuilder.(CommandLineBuilder.java:73)
> [cobertura-merge] at 
> net.sourceforge.cobertura.merge.MergeMain.merge(MergeMain.java:66)
> [cobertura-merge] at 
> net.sourceforge.cobertura.merge.MergeMain.main(MergeMain.java:77)
> [cobertura-merge] Caused by: java.lang.ClassNotFoundException: 
> org.slf4j.LoggerFactory
> [cobertura-merge] at 
> java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> [cobertura-merge] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> [cobertura-merge] at 
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> [cobertura-merge] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> [cobertura-merge] ... 3 more
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 2.265 s
> [INFO] Finished at: 2016-05-31T18:59:31+03:00
> [INFO] Final Memory: 9M/119M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-antrun-plugin:1.8:run (cobertura-merge-base) 
> on project cobertura-report: An Ant BuildException has occured: Error running 
> reports. See messages above.
> [ERROR] around Ant part ... datafile="C:\...\cobertura\target/cobertura/cobertura.ser">... @ 5:114 in 
> C:\..\cobertura\target\antrun\build-main.xml
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> The pom used:
> {code}
> 
>xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
>   xmlns="http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
>   4.0.0
>   
>   2.1.1
>   
>   org.tests
>   cobertura-report
>   1.12-SNAPSHOT
>   Cobertura Merge test
>   pom
>   
>   cobertura-report
>   
>   
>   org.apache.maven.plugins
>   maven-antrun-plugin
>   1.8
>   
>   
>   org.slf4j
>   
> slf4j-api
>   1.7.5
>   
>   
>   
> net.sourceforge.cobertura
>   
> cobertura
>  

[jira] [Commented] (SUREFIRE-1226) Surefire trims all stack trace elements except those in the test that failed

[Jesse Glick (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424904#comment-15424904
 ] 

Jesse Glick commented on SUREFIRE-1226:
---

[~tibor17] I agree with [~jloc...@redhat.com]’s expectation. Was unpleasantly 
surprised to update to 2.19.1 (so as to pick up SUREFIRE-1138) and finding test 
output like

{code:none}
java.lang.NullPointerException
at 
jenkins.plugins.git.AbstractGitSCMSourceTest.fileAt(AbstractGitSCMSourceTest.java:89)
at 
jenkins.plugins.git.AbstractGitSCMSourceTest.retrieveRevision(AbstractGitSCMSourceTest.java:76)
{code}

(nonsensical since line 89 of the test could not possibly throw this 
exception!) where before I had gotten

{code:none}
java.lang.NullPointerException
at 
jenkins.plugins.git.AbstractGitSCMSource.resolveGitTool(AbstractGitSCMSource.java:157)
at 
jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:269)
at jenkins.scm.api.SCMSource.retrieve(SCMSource.java:295)
at 
jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:358)
at jenkins.scm.api.SCMSource.fetch(SCMSource.java:277)
at 
jenkins.plugins.git.AbstractGitSCMSourceTest.fileAt(AbstractGitSCMSourceTest.java:89)
at 
jenkins.plugins.git.AbstractGitSCMSourceTest.retrieveRevision(AbstractGitSCMSourceTest.java:76)
{code}

which clearly indicates the problem.

If you are going to trim stack frames inside the test (which I do not advise), 
you need to leave *some* clue to users, so they do not have to spend an hour 
bisecting and searching bug trackers! For example

{code:none}
java.lang.NullPointerException
…5 stack frames elided, set trimStackTrace=false to display
at 
jenkins.plugins.git.AbstractGitSCMSourceTest.fileAt(AbstractGitSCMSourceTest.java:89)
at 
jenkins.plugins.git.AbstractGitSCMSourceTest.retrieveRevision(AbstractGitSCMSourceTest.java:76)
{code}

> Surefire trims all stack trace elements except those in the test that failed
> 
>
> Key: SUREFIRE-1226
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1226
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19
>Reporter: Jiri Locker
>Assignee: Tibor Digana
>Priority: Minor
> Attachments: mvn_stacktrace.tar.gz
>
>
> This looks like a re-occurrence of SUREFIRE-992 but now the stack trace is 
> even more trimmed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6080) New scope for non-functional dependencies

[Paul Benedict (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424851#comment-15424851
 ] 

Paul Benedict commented on MNG-6080:


In a WAR project, yes, using {{provided}} would work because the ZIP would be 
consumed directly by the WAR. The transitive nature of {{provided}} wouldn't 
matter here. You are correct. Yet, I want to be careful in my analysis and make 
sure my use case isn't the wrong measuring stick for this new scope. 

> New scope for non-functional dependencies
> -
>
> Key: MNG-6080
> URL: https://issues.apache.org/jira/browse/MNG-6080
> Project: Maven
>  Issue Type: New Feature
>  Components: Dependencies
>Affects Versions: 3.3.9
>Reporter: Paul Benedict
>Assignee: Paul Benedict
>Priority: Critical
>
> Maven currently lacks a scope for artifacts that should not be part of the 
> classpath. The classpath is the path that the Java Runtime Environment (JRE) 
> searches for classes and other resource files. Given that the classpath is 
> Java specific, this feature request can be generalized to accommodate 
> artifacts that are not code related (directly or indirectly). It is neither 
> code that executes (like a .class file = "directly") nor a resource file 
> intimately linked to executable code (like a .properties file = "indirectly").
> For example, an organization may with to establish a Maven project that 
> contains common look-and-feel elements to brand all their web applications. 
> This project could be a ZIP archive to be included in downstream projects, in 
> which each build explodes the archive into their respective web application 
> context roots.
> Two names in the running for the new scope are {{"asset"}} and {{"reactor"}}. 
> They are nearly equal but have a different slight emphasis. The {{"asset"}} 
> name emphasizes purpose of artifact. The {{"reactor"}} name emphasizes 
> purpose within the build. The Maven Team should decide among these two or 
> propose a third. 
> Thread where discussion originated:
> http://mail-archives.apache.org/mod_mbox/maven-dev/201608.mbox/%3CCABLGb9x5e3fE25Qj9DwvCsCSa1Dwe_e6%2BOmWjL0ZbQ07HLEm8g%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MDEPLOY-152) updateReleaseInfo for deploy-file does not work with Maven 3

[Paresh Khond (JIRA)]

[ 
https://issues.apache.org/jira/browse/MDEPLOY-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424668#comment-15424668
 ] 

Paresh Khond commented on MDEPLOY-152:
--

updateReleaseInfo for deploy-file does not work with Maven 3

[DEBUG]   (f) offline = false
[DEBUG]   (f) packaging = txt
[DEBUG]   (f) repositoryId = nexus.repo
[DEBUG]   (f) repositoryLayout = default
[DEBUG]   (f) uniqueVersion = true
[DEBUG]   (f) updateReleaseInfo = false

1.0.4

20160817143735

Trying to set this as part of mvn deploy:deploy-file -DupdateReleaseInfo=false 
- but still updating the releaseinfo in maven-metadata.xml

> updateReleaseInfo for deploy-file does not work with Maven 3
> 
>
> Key: MDEPLOY-152
> URL: https://issues.apache.org/jira/browse/MDEPLOY-152
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Affects Versions: 2.7
> Environment: Linux, maven 3.0.4
>Reporter: Ivan Sopov
> Fix For: waiting-for-feedback
>
>
> When deploying file with {{-DupdateReleaseInfo=true}} with maven3 
> {{}} tag is not updated/created, but with maven2 
> everything is good. Here is the full log:
> {noformat}
> $mvn -version
>   Apache Maven 3.0.4 (r1232337; 2012-01-17 10:44:56+0200)
>   Maven home: /home/user/java/apache-maven-3.0.4
>   Java version: 1.7.0_04, vendor: Oracle Corporation
>   Java home: /opt/jdk1.7.0_04/jre
>   Default locale: en_US, platform encoding: UTF-8
>   OS name: "linux", version: "2.6.32-40-generic-pae", arch: "i386", 
> family: "unix"
> $mvn -e -DupdateReleaseInfo=true 
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file 
> -Durl=file:///home/user/test/ldClientDeployTest/repository 
> -Dfile=/home/user/java/workspace/testing/mvnDeployFileIssue/test-proj/target/test-proj-1.0-SNAPSHOT.jar
>  
> -DpomFile=/home/user/java/workspace/testing/mvnDeployFileIssue/test-proj/pom.xml
>  -Dpackaging=jar
> $cat 
> /home/user/test/ldClientDeployTest/repository/com/example/test-proj/maven-metadata.xml
>  
>   
>   
> com.example
> test-proj
> 
>   
> 1.0-SNAPSHOT
>   
>   20120702111039
> 
>   
> $M2_HOME=/home/user/java/apache-maven-2.2.1/
> $PATH=$M2_HOME/bin:$PATH
> $mvn -version
>   Apache Maven 2.2.1 (r801777; 2009-08-06 22:16:01+0300)
>   Java version: 1.7.0_04
>   Java home: /opt/jdk1.7.0_04/jre
>   Default locale: en_US, platform encoding: UTF-8
>   OS name: "linux" version: "2.6.32-40-generic-pae" arch: "i386" Family: 
> "unix"
> $cat 
> /home/user/test/ldClientDeployTest/repository/com/example/test-proj/maven-metadata.xml
>  
>   
>   
> com.example
> test-proj
> 
>   1.0-SNAPSHOT
>   
> 1.0-SNAPSHOT
>   
>   20120702111359
> 
>   
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6024) maven-antrun-plugin:instrument failing NoClassDefFoundError: org/slf4j/LoggerFactory

[S V Mohana Rao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

S V Mohana Rao updated MNG-6024:

Attachment: maven-core-slf4j-issue.zip

Please run the following command to simulate error.

mvn clean install
mvn verify -Dcobertura=true -Pcobertura

> maven-antrun-plugin:instrument failing NoClassDefFoundError: 
> org/slf4j/LoggerFactory
> 
>
> Key: MNG-6024
> URL: https://issues.apache.org/jira/browse/MNG-6024
> Project: Maven
>  Issue Type: Bug
>  Components: Class Loading
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
> Environment: Window 7, JDK 1.8.0_40
>Reporter: S V Mohana Rao
>Priority: Blocker
> Attachments: maven-core-slf4j-issue.zip, mvn-coreslf4j-issue.txt
>
>
> Related issues : MNG-5783, MNG-5817. I was using maven-antrun-plugin added 
> dependency cobertura which requires slf4j-api dependent jar. Even i tried 
> using 3.4.0-SNAPSHOT version but problem persists. As i was observed it's 
> been excluded from the child dependent artifacts of cobertura cause it's part 
> maven core. But it's not referring from maven core which hasn't been added 
> class path. 



--
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

[Jean-Luc Derrien (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424541#comment-15424541
 ] 

Jean-Luc Derrien edited comment on SUREFIRE-1263 at 8/17/16 1:50 PM:
-

[~tibor17], I've been to reproduce the problem with 
https://github.com/apache/maven-surefire/tree/master/surefire-integration-tests/src/test/resources/surefire-1082-parallel-junit-parameterized
 by adding this config to {{maven-surefire-plugin}}:
{noformat}
--- 
a/surefire-integration-tests/src/test/resources/surefire-1082-parallel-junit-parameterized/pom.xml
+++ 
b/surefire-integration-tests/src/test/resources/surefire-1082-parallel-junit-parameterized/pom.xml
@@ -60,6 +60,10 @@
   
   
 maven-surefire-plugin
+
+  all
+  2
+
   
 
   
{noformat}


was (Author: jderrien):
[~tibor17], I've been to reproduce the problem with 
https://github.com/apache/maven-surefire/tree/master/surefire-integration-tests/src/test/resources/surefire-1082-parallel-junit-parameterized
 by adding this config to {{maven-surefire-plugin}}:
{noformat}
  
maven-surefire-plugin

  all
  2

  
{noformat}

> 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
>
> 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

[Jean-Luc Derrien (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424541#comment-15424541
 ] 

Jean-Luc Derrien commented on SUREFIRE-1263:


[~tibor17], I've been to reproduce the problem with 
https://github.com/apache/maven-surefire/tree/master/surefire-integration-tests/src/test/resources/surefire-1082-parallel-junit-parameterized
 by adding this config to {{maven-surefire-plugin}}:
{noformat}
  
maven-surefire-plugin

  all
  2

  
{noformat}

> 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
>
> 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-323) Running a single test using -Dtest has no effect

[Jin Kwon (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424003#comment-15424003
 ] 

Jin Kwon commented on SUREFIRE-323:
---

And {{-Dit.test=}} also doesn't do anything at all

> Running a single test using -Dtest has no effect
> 
>
> Key: SUREFIRE-323
> URL: https://issues.apache.org/jira/browse/SUREFIRE-323
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: java version "1.5.0_09"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode)
>Reporter: Graham Leggett
>Assignee: Brett Porter
>
> Using the -D option from the command line to run a test as per the 
> instructions at 
> http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html,
>  the test is ignored.
> The test is not configured within the pom, because the test should only be 
> run by hand, not as part of the build. Thus the need to run the test on its 
> own.
> bash-3.00$ mvn -Dtest=**/*TestConcurrency test
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Building Alchemy Measure
> [INFO]task-segment: [test]
> [INFO] 
> 
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.
> The following command line options also do not work:
> bash-3.00$ mvn -Dtest=TestConcurrency test
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Building Alchemy Measure
> [INFO]task-segment: [test]
> [INFO] 
> 
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)