[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=15451191#comment-15451191
]
Hemanth commented on SUREFIRE-1245:
---
Sorry for the late reply TIBOR. Caught up with alot of work.
I don't know why the bad file descriptor issue is coming. I have used
explicit waits on a regular basis. Haven't I given you the project that
replicates this issue? If I haven't I will give you again.
> 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
>
>
>
>
[jira] [Commented] (SUREFIRE-1268) With JUnit listener, redirectTestOutputToFile is ignored
[
https://issues.apache.org/jira/browse/SUREFIRE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451033#comment-15451033
]
Francesco Chicchiriccò commented on SUREFIRE-1268:
--
Thank you very much!
> With JUnit listener, redirectTestOutputToFile is ignored
>
>
> Key: SUREFIRE-1268
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1268
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Linux
>Reporter: Francesco Chicchiriccò
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> When specifying, according to [this
> doc|http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_Custom_Listeners_and_Reporters],
> a JUnit listener, the test output is sent to STDOUT, even though
> {{redirectTestOutputToFile}} is set to {{true}}.
> This happens with log4j2 configuration for {{SYSTEM_OUT}}, regular
> {{System.out.println}} works fine.
> With no {{properties}} element, {{redirectTestOutputToFile}} is honored.
--
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=15450570#comment-15450570
]
Tibor Digana commented on SUREFIRE-1245:
[~hemanth.BS]
Please answer my questions above in Jira; otherwise I have to consider this
issue as no interest on your side and close it which means you can still reopen
it again.
> 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
>
[jira] [Commented] (SUREFIRE-1268) With JUnit listener, redirectTestOutputToFile is ignored
[
https://issues.apache.org/jira/browse/SUREFIRE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450480#comment-15450480
]
Hudson commented on SUREFIRE-1268:
--
SUCCESS: Integrated in Jenkins build maven-surefire #1605 (See
[https://builds.apache.org/job/maven-surefire/1605/])
[SUREFIRE-1268] With JUnit listener, redirectTestOutputToFile is ignored
(tibor17: rev 658230b69241fc87588e9b007391f9ae4a2b416a)
* (edit)
surefire-providers/surefire-junit47/src/main/java/org/apache/maven/surefire/junitcore/JUnitCoreProvider.java
* (edit)
surefire-providers/surefire-junit4/src/main/java/org/apache/maven/surefire/junit4/JUnit4Provider.java
> With JUnit listener, redirectTestOutputToFile is ignored
>
>
> Key: SUREFIRE-1268
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1268
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Linux
>Reporter: Francesco Chicchiriccò
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> When specifying, according to [this
> doc|http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_Custom_Listeners_and_Reporters],
> a JUnit listener, the test output is sent to STDOUT, even though
> {{redirectTestOutputToFile}} is set to {{true}}.
> This happens with log4j2 configuration for {{SYSTEM_OUT}}, regular
> {{System.out.println}} works fine.
> With no {{properties}} element, {{redirectTestOutputToFile}} is honored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1268) With JUnit listener, redirectTestOutputToFile is ignored
[
https://issues.apache.org/jira/browse/SUREFIRE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1268.
--
Resolution: Fixed
commit 658230b69241fc87588e9b007391f9ae4a2b416a
> With JUnit listener, redirectTestOutputToFile is ignored
>
>
> Key: SUREFIRE-1268
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1268
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Linux
>Reporter: Francesco Chicchiriccò
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> When specifying, according to [this
> doc|http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_Custom_Listeners_and_Reporters],
> a JUnit listener, the test output is sent to STDOUT, even though
> {{redirectTestOutputToFile}} is set to {{true}}.
> This happens with log4j2 configuration for {{SYSTEM_OUT}}, regular
> {{System.out.println}} works fine.
> With no {{properties}} element, {{redirectTestOutputToFile}} is honored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPOM-132) assembly plugin should use posix, not gnu for tarLongFileMode
[
https://issues.apache.org/jira/browse/MPOM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450330#comment-15450330
]
Christopher Tubbs commented on MPOM-132:
Cool stuffs. Thanks. Sorry to bother, but one more note. Now that the property
has been set by default in the {{}} section, it could be entirely
removed in the maven-assembly-plugin configuration, since that's redundant.
Right now, it will always be overridden by the property anyway. :)
> assembly plugin should use posix, not gnu for tarLongFileMode
> -
>
> Key: MPOM-132
> URL: https://issues.apache.org/jira/browse/MPOM-132
> Project: Maven POMs
> Issue Type: Task
> Components: asf
>Reporter: Christopher Tubbs
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: ASF-19
>
>
> {{gnu}} causes some issues on some
> platforms. Most modern versions of tar support the newer {{posix}} mode,
> which supports all the features {{gnu}} does, plus more.
> Instead of the release profile's execution of the source-release-assembly
> using the above setting, that should be removed from the assembly
> configuration, and instead, the parent pom should add the following to the
> {{}}:
> {{posix}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPOM-137) Upgrade maven-scm-plugin to 1.9.5
[ https://issues.apache.org/jira/browse/MPOM-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450231#comment-15450231 ] Hudson commented on MPOM-137: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #157 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/157/]) [MPOM-137] Upgrade maven-scm-plugin to 1.9.5 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1758471]) * (edit) pom.xml > Upgrade maven-scm-plugin to 1.9.5 > - > > Key: MPOM-137 > URL: https://issues.apache.org/jira/browse/MPOM-137 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-19 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-132) assembly plugin should use posix, not gnu for tarLongFileMode
[
https://issues.apache.org/jira/browse/MPOM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450232#comment-15450232
]
Hudson commented on MPOM-132:
-
SUCCESS: Integrated in Jenkins build ASF Parent Pom #157 (See
[https://builds.apache.org/job/ASF%20Parent%20Pom/157/])
[MPOM-132] assembly plugin should use posix, not gnu for tarLongFileMode
o Followup missed to set the configuration for maven-assembly-plugin
correctly. (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1758470])
* (edit) pom.xml
> assembly plugin should use posix, not gnu for tarLongFileMode
> -
>
> Key: MPOM-132
> URL: https://issues.apache.org/jira/browse/MPOM-132
> Project: Maven POMs
> Issue Type: Task
> Components: asf
>Reporter: Christopher Tubbs
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: ASF-19
>
>
> {{gnu}} causes some issues on some
> platforms. Most modern versions of tar support the newer {{posix}} mode,
> which supports all the features {{gnu}} does, plus more.
> Instead of the release profile's execution of the source-release-assembly
> using the above setting, that should be removed from the assembly
> configuration, and instead, the parent pom should add the following to the
> {{}}:
> {{posix}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MPOM-137) Upgrade maven-scm-plugin to 1.9.5
[ https://issues.apache.org/jira/browse/MPOM-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPOM-137. Resolution: Fixed Assignee: Karl Heinz Marbaise Done in [r1758471|https://svn.apache.org/r1758471] > Upgrade maven-scm-plugin to 1.9.5 > - > > Key: MPOM-137 > URL: https://issues.apache.org/jira/browse/MPOM-137 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-19 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MPOM-132) assembly plugin should use posix, not gnu for tarLongFileMode
[
https://issues.apache.org/jira/browse/MPOM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450160#comment-15450160
]
Karl Heinz Marbaise edited comment on MPOM-132 at 8/30/16 9:09 PM:
---
Done in [r1758470|https://svn.apache.org/r1758470]
was (Author: khmarbaise):
Done i [r1758470|https://svn.apache.org/r1758470]
> assembly plugin should use posix, not gnu for tarLongFileMode
> -
>
> Key: MPOM-132
> URL: https://issues.apache.org/jira/browse/MPOM-132
> Project: Maven POMs
> Issue Type: Task
> Components: asf
>Reporter: Christopher Tubbs
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: ASF-19
>
>
> {{gnu}} causes some issues on some
> platforms. Most modern versions of tar support the newer {{posix}} mode,
> which supports all the features {{gnu}} does, plus more.
> Instead of the release profile's execution of the source-release-assembly
> using the above setting, that should be removed from the assembly
> configuration, and instead, the parent pom should add the following to the
> {{}}:
> {{posix}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MPOM-132) assembly plugin should use posix, not gnu for tarLongFileMode
[
https://issues.apache.org/jira/browse/MPOM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MPOM-132.
Resolution: Fixed
Done i [r1758470|https://svn.apache.org/r1758470]
> assembly plugin should use posix, not gnu for tarLongFileMode
> -
>
> Key: MPOM-132
> URL: https://issues.apache.org/jira/browse/MPOM-132
> Project: Maven POMs
> Issue Type: Task
> Components: asf
>Reporter: Christopher Tubbs
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: ASF-19
>
>
> {{gnu}} causes some issues on some
> platforms. Most modern versions of tar support the newer {{posix}} mode,
> which supports all the features {{gnu}} does, plus more.
> Instead of the release profile's execution of the source-release-assembly
> using the above setting, that should be removed from the assembly
> configuration, and instead, the parent pom should add the following to the
> {{}}:
> {{posix}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1276) Document handling of multiline exception messages
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1276.
--
Resolution: Fixed
commit 0aeceecc3b85d1133a1a2f2335a89950689e33bb
> Document handling of multiline exception messages
> -
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>Assignee: Tibor Digana
> Labels: documentation
> Fix For: 2.19.2
>
>
> I am throwing an exception whose message contains newlines for readability.
> When {{}} is true (the default value) Surefire is removing
> all newlines.
> Expected behavior: Consider moving this functionality out of
> {{}} into its own parameter. Regardless of which parameter
> enables this behavior, please document it at
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html ...
> right now there is no mention of this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1276) Document handling of multiline exception messages
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1276:
---
Fix Version/s: 2.19.2
> Document handling of multiline exception messages
> -
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>Assignee: Tibor Digana
> Labels: documentation
> Fix For: 2.19.2
>
>
> I am throwing an exception whose message contains newlines for readability.
> When {{}} is true (the default value) Surefire is removing
> all newlines.
> Expected behavior: Consider moving this functionality out of
> {{}} into its own parameter. Regardless of which parameter
> enables this behavior, please document it at
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html ...
> right now there is no mention of this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1276) Document handling of multiline exception messages
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449843#comment-15449843
]
Gili commented on SUREFIRE-1276:
[~tibor17] Sorry for the delay. See
https://github.com/apache/maven-surefire/pull/116
> Document handling of multiline exception messages
> -
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>Assignee: Tibor Digana
> Labels: documentation
>
> I am throwing an exception whose message contains newlines for readability.
> When {{}} is true (the default value) Surefire is removing
> all newlines.
> Expected behavior: Consider moving this functionality out of
> {{}} into its own parameter. Regardless of which parameter
> enables this behavior, please document it at
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html ...
> right now there is no mention of this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MCOMPILER-269) Support modulepath (Java9/Jigsaw)
[ https://issues.apache.org/jira/browse/MCOMPILER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449813#comment-15449813 ] Hudson commented on MCOMPILER-269: -- SUCCESS: Integrated in Jenkins build maven-plugins #7208 (See [https://builds.apache.org/job/maven-plugins/7208/]) [MCOMPILER-269] Support modulepath (Java9/Jigsaw) (rfscholte: [http://svn.apache.org/viewvc/?view=rev&rev=1758438]) * (edit) maven-compiler-plugin/pom.xml * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/invoker.properties * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/pom.xml * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/main * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/main/java * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/main/java/com * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/main/java/com/foo * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/main/java/com/foo/MyClass.java * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/main/java/module-info.java * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/test * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/test/java * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/test/java/com * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/test/java/com/foo * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/src/test/java/com/foo/MyTest.java * (add) maven-compiler-plugin/src/it/MCOMPILER-268_modulepath/verify.groovy * (edit) maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java * (edit) maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/CompilerMojo.java * (edit) maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java * (edit) maven-compiler-plugin/src/test/java/org/apache/maven/plugin/compiler/CompilerMojoTestCase.java > Support modulepath (Java9/Jigsaw) > - > > Key: MCOMPILER-269 > URL: https://issues.apache.org/jira/browse/MCOMPILER-269 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: 3.6 > > > http://openjdk.java.net/jeps/261 describes which arguments to use to make > proper use of modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MCOMPILER-269) Support modulepath (Java9/Jigsaw)
[ https://issues.apache.org/jira/browse/MCOMPILER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MCOMPILER-269. Resolution: Fixed Fix Version/s: 3.6 Fixed in [r1758438|http://svn.apache.org/viewvc?rev=1758438&view=rev] > Support modulepath (Java9/Jigsaw) > - > > Key: MCOMPILER-269 > URL: https://issues.apache.org/jira/browse/MCOMPILER-269 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: 3.6 > > > http://openjdk.java.net/jeps/261 describes which arguments to use to make > proper use of modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1268) With JUnit listener, redirectTestOutputToFile is ignored
[
https://issues.apache.org/jira/browse/SUREFIRE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1268:
---
Fix Version/s: 2.19.2
> With JUnit listener, redirectTestOutputToFile is ignored
>
>
> Key: SUREFIRE-1268
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1268
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Linux
>Reporter: Francesco Chicchiriccò
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> When specifying, according to [this
> doc|http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_Custom_Listeners_and_Reporters],
> a JUnit listener, the test output is sent to STDOUT, even though
> {{redirectTestOutputToFile}} is set to {{true}}.
> This happens with log4j2 configuration for {{SYSTEM_OUT}}, regular
> {{System.out.println}} works fine.
> With no {{properties}} element, {{redirectTestOutputToFile}} is honored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1268) With JUnit listener, redirectTestOutputToFile is ignored
[
https://issues.apache.org/jira/browse/SUREFIRE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449690#comment-15449690
]
Tibor Digana commented on SUREFIRE-1268:
I see now. The problem is that the listeners are instantiated first in Surefire
and the stream System.out gets replaced after that. Most probably LOG4J handles
the original System.out when the static class context was called.
I should reorder listener and call of setOut() in providers.
> With JUnit listener, redirectTestOutputToFile is ignored
>
>
> Key: SUREFIRE-1268
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1268
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Linux
>Reporter: Francesco Chicchiriccò
>Assignee: Tibor Digana
>
> When specifying, according to [this
> doc|http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_Custom_Listeners_and_Reporters],
> a JUnit listener, the test output is sent to STDOUT, even though
> {{redirectTestOutputToFile}} is set to {{true}}.
> This happens with log4j2 configuration for {{SYSTEM_OUT}}, regular
> {{System.out.println}} works fine.
> With no {{properties}} element, {{redirectTestOutputToFile}} is honored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1276) Document handling of multiline exception messages
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449657#comment-15449657
]
Tibor Digana commented on SUREFIRE-1276:
[~cowwoc]
Do you have time for this?
> Document handling of multiline exception messages
> -
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>Assignee: Tibor Digana
> Labels: documentation
>
> I am throwing an exception whose message contains newlines for readability.
> When {{}} is true (the default value) Surefire is removing
> all newlines.
> Expected behavior: Consider moving this functionality out of
> {{}} into its own parameter. Regardless of which parameter
> enables this behavior, please document it at
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html ...
> right now there is no mention of this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1255) Surefire 2.19.1 hangs before starting test execution
[
https://issues.apache.org/jira/browse/SUREFIRE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449411#comment-15449411
]
Maximilian Michels commented on SUREFIRE-1255:
--
I didn't get what Surefire does but I'm assuming it just wraps the standard out
and parses and removes its messages from the stdout stream.
log4j doesn't appear to change the standard out:
https://github.com/search?l=&q=setOut+repo%3Aapache%2Flog4j&ref=advsearch&type=Code&utf8=%E2%9C%93
Further, if you look at {{ConsoleAppender}} you'll see that it just prints to
System.out but never replaces it.
> Surefire 2.19.1 hangs before starting test execution
>
>
> Key: SUREFIRE-1255
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1255
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.19.1
>Reporter: Maximilian Michels
>Assignee: Tibor Digana
>Priority: Critical
>
> Seeing the same error as SUREFIRE-1193 in Apache Flink builds after upgrading
> from 2.18.1 to 2.19.1. No errors, builds just gets stuck at the beginning of
> tests with no log output from the test itself, e.g.
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/137118454/log.txt
> After a couple of minutes Surefire reports
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test
> (integration-tests) on project flink-scala-shell_2.10: ExecutionException The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was /bin/sh -c cd
> /home/travis/build/mxm/flink/flink-scala-shell/target &&
> /usr/lib/jvm/java-8-oracle/jre/bin/java -Xms256m -Xmx800m -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -jar
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefirebooter372520169616801479.jar
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire8229439069544382018tmp
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire_26373613144387982724tmp
> [ERROR] -> [Help 1]
> {noformat}
> We have a a couple of test classes that suffer from this problem. Tests don't
> read from STDIN or replace it. Switching back to 2.18.1 eliminates the
> problem (Ran over 100 builds). It seems to be a race condition because it
> only occurs every once in a while, i.e. ~ 2 out of 10 builds on Travis. I
> haven't been able to reproduce the problem locally.
> More logs:
> https://s3.amazonaws.com/flink-logs-us/travis-artifacts/mxm/flink/849/849.1.tar.gz
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MPLUGIN-313) Error injecting JavaAnnotationsMojoDescriptorExtractor
[
https://issues.apache.org/jira/browse/MPLUGIN-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MPLUGIN-313.
--
Resolution: Cannot Reproduce
Assignee: Robert Scholte
If you have a setup to reproduce it, add it as a MNG bug. I'll close it here.
> Error injecting JavaAnnotationsMojoDescriptorExtractor
> --
>
> Key: MPLUGIN-313
> URL: https://issues.apache.org/jira/browse/MPLUGIN-313
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: API
>Affects Versions: 3.5
>Reporter: Paul Benedict
>Assignee: Robert Scholte
>Priority: Blocker
>
> In the latest 3.5 snapshot, an exception prevents the building of a Mojo. I
> tagged this as a "blocker" because I cannot find a workaround.
> Messages and stack trace:
> {code}
> [WARNING] The POM for
> org.apache.maven.plugin-tools:maven-plugin-tools-annotations:jar:3.5-20160826.210808-25
> is invalid, transitive dependencies (if any) will not be available, enable
> debug logging for more details
> [INFO] java-javadoc mojo extractor found 0 mojo descriptor.
> [WARNING] Error injecting:
> org.apache.maven.tools.plugin.extractor.annotations.JavaAnnotationsMojoDescriptorExtractor
> java.lang.NoClassDefFoundError:
> org/codehaus/plexus/archiver/manager/NoSuchArchiverException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
> at java.lang.Class.getDeclaredConstructors(Class.java:2020)
> at
> com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
> at
> com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:99)
> at
> com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:657)
> at
> com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:875)
> at
> com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:798)
> at
> com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:281)
> at
> com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:213)
> at
> com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:998)
> at
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:994)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1044)
> at
> org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
> at
> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:54)
> at
> com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
> at
> org.eclipse.sisu.bean.BeanScheduler$Activator.onProvision(BeanScheduler.java:176)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126)
> at
> com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
> at
> com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:46)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1066)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at
> com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:36)
> at
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at
> com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1009)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1059)
> at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1005)
> at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
> at
> org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)
> at java.util.AbstractMap.get(AbstractMap.java:187)
> at
> org.apache.maven.tools.
[jira] [Commented] (MPOM-132) assembly plugin should use posix, not gnu for tarLongFileMode
[
https://issues.apache.org/jira/browse/MPOM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448663#comment-15448663
]
Karl Heinz Marbaise commented on MPOM-132:
--
Hi, sure you are right...I will fix thanks for the catch.
> assembly plugin should use posix, not gnu for tarLongFileMode
> -
>
> Key: MPOM-132
> URL: https://issues.apache.org/jira/browse/MPOM-132
> Project: Maven POMs
> Issue Type: Task
> Components: asf
>Reporter: Christopher Tubbs
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: ASF-19
>
>
> {{gnu}} causes some issues on some
> platforms. Most modern versions of tar support the newer {{posix}} mode,
> which supports all the features {{gnu}} does, plus more.
> Instead of the release profile's execution of the source-release-assembly
> using the above setting, that should be removed from the assembly
> configuration, and instead, the parent pom should add the following to the
> {{}}:
> {{posix}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5576) Allow continuous delivery friendly versions
[
https://issues.apache.org/jira/browse/MNG-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448357#comment-15448357
]
Vincent Massol commented on MNG-5576:
-
The way it could be done:
* If you're in a multi module project and the parent can be found in the
filesystem, then resolve project.version by traversing the parent hierarchy
upward till you find a pom.xml containing a {{}} element.
* If you're in a single module and/or the parent is not found on the filesystem
(nor in {{.mvn/maven.config}}), and the current pom.xml doesn't define a
{{}} element then emit an error that project.version is undefined and
maybe allow users to pass it on the command line (not even sure that it's
needed).
Note that omimtting completely omit the {{}} in the {{}}
element would normally resolve it to the latest released version which may not
be what we want.
Thanks for your answers. When i read the release notes for 3.2.1 I was happy
initially to see the ability to support some variables for parent versions.
After looking at it, I was disappointed that it was only working for some edge
cases and I was wondering if there was a technical reason.
Keep the good of making Maven progress! (which I dropped years ago on my side
to dedicate my time to xwiki).
> Allow continuous delivery friendly versions
> ---
>
> Key: MNG-5576
> URL: https://issues.apache.org/jira/browse/MNG-5576
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.1.1
>Reporter: Jason van Zyl
> Fix For: 3.2.1
>
>
> Currently warnings will be emitted when there are expressions in versions, a
> few exceptions should be deemed valid to make continuous delivery easier. The
> use case is to allow easy versioning of an entire multi-module build that can
> take a version from an external source like SCM. These are the types of
> exceptions that will be allowed:
> 1.0.0.$\{changelist}
> 1.0.0.$\{revision}
> 1.0.0.$\{sha1}
> When a whole build is versioned like this we can avoid churning the POMs in
> the SCM which makes it a lot easier to see the actual changes in the project.
> Not a complete solution for continuous delivery but is a step in the right
> direction and doesn't interfere with currently behavior as it is currently
> allowed, just warned against.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
