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

2016-08-17 Thread 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:

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

2016-08-17 Thread 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. >

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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:

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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:

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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]

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

2016-08-17 Thread 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 >

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

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

2016-08-17 Thread 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

[jira] [Comment Edited] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests

2016-08-17 Thread 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:

[jira] [Commented] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests

2016-08-17 Thread 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

[jira] [Commented] (SUREFIRE-323) Running a single test using -Dtest has no effect

2016-08-17 Thread 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