[jira] [Updated] (MSHARED-580) Doclint errors in maven-artifact-transfer
[
https://issues.apache.org/jira/browse/MSHARED-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikolaj Izdebski updated MSHARED-580:
-
Attachment: MSHARED-580.patch
> Doclint errors in maven-artifact-transfer
> -
>
> Key: MSHARED-580
> URL: https://issues.apache.org/jira/browse/MSHARED-580
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-3.0.0
> Environment: Java 8
>Reporter: Mikolaj Izdebski
> Attachments: MSHARED-580.patch
>
>
> Latest maven-artifact-transfer (SVN revision 1753832) does not compile with
> Java 8 due to error in Javadoc and strict doclint.
> {code}
> [ERROR]
> /home/kojan/pkg/maven-artifact-transfer/maven-artifact-transfer/src/main/java/org/apache/maven/shared/repository/internal/Maven30RepositoryManager.java:169:
> error: @param name not found
> [ERROR] * @param typeRegistry {link ArtifactType}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MSHARED-580) Doclint errors in maven-artifact-transfer
Mikolaj Izdebski created MSHARED-580:
Summary: Doclint errors in maven-artifact-transfer
Key: MSHARED-580
URL: https://issues.apache.org/jira/browse/MSHARED-580
Project: Maven Shared Components
Issue Type: Bug
Components: maven-artifact-transfer
Affects Versions: maven-artifact-transfer-3.0.0
Environment: Java 8
Reporter: Mikolaj Izdebski
Latest maven-artifact-transfer (SVN revision 1753832) does not compile with
Java 8 due to error in Javadoc and strict doclint.
{code}
[ERROR]
/home/kojan/pkg/maven-artifact-transfer/maven-artifact-transfer/src/main/java/org/apache/maven/shared/repository/internal/Maven30RepositoryManager.java:169:
error: @param name not found
[ERROR] * @param typeRegistry {link ArtifactType}
{code}
--
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=15432050#comment-15432050
]
Tibor Digana commented on SUREFIRE-1276:
perhaps faq and
https://maven.apache.org/surefire/maven-failsafe-plugin/newerrorsummary.html
https://github.com/apache/maven-surefire/blob/master/maven-surefire-plugin/src/site/fml/faq.fml
https://github.com/apache/maven-surefire/blob/master/maven-surefire-plugin/src/site/markdown/newerrorsummary.md
> 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=15432029#comment-15432029
]
Tibor Digana commented on SUREFIRE-1255:
The problematic project was {{flink-scala-shell}}. In the logs it seems the
tests run in parallel. Can you try to temporarily disable parallel execution? I
want to exclude some side effects.
> 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
>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] [Commented] (SUREFIRE-1216) TEST-*.xml files generated by Surefire are invalid
[
https://issues.apache.org/jira/browse/SUREFIRE-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432016#comment-15432016
]
ASF GitHub Bot commented on SUREFIRE-1216:
--
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/110
@justinharringa
We are close to cut release version 2.19.2. Only 2 issues are still open
and other critical/blocker issues must be fixed in 2.19.3.
> TEST-*.xml files generated by Surefire are invalid
> --
>
> Key: SUREFIRE-1216
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1216
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Mirko Friedenhagen
>Assignee: Mirko Friedenhagen
> Fix For: 2.19.2
>
>
> See SUREFIRE-964 as well. The XML produced is invalid because
> {{schemaLocation}} *must* include two URIs, as outlined in
> [xmlschema-1|http://www.w3.org/TR/xmlschema-1/#schema-loc].
> Because of this, the Xerces parser fails in the Jenkins XUnit plugin and e.g.
> IntelliJ is not able to parse the file correctly.
> Suggested solution is to replace {{xsi:schemaLocation}} by
> {{xsi:noNamespaceSchemaLocation}}, which fixes this for the Unit plugin as
> well the file is parseable by IntelliJ.
--
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=15432001#comment-15432001
]
Gili commented on SUREFIRE-1276:
[~tibor17] What file do you expect me to submit a PR for this documentation
change? When I click on "Release Notes" on your website, I get an empty page:
https://maven.apache.org/surefire/maven-surefire-plugin/jira-report.html
I was thinking we should add this to the release notes of 2.19 (which contained
SUREFIRE-986). I'm thinking we should mention this elsewhere (FAQ maybe?), but
I can't think of anywhere else that a user would look in to discover this
feature. Any ideas?
> 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-1216) TEST-*.xml files generated by Surefire are invalid
[
https://issues.apache.org/jira/browse/SUREFIRE-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431986#comment-15431986
]
ASF GitHub Bot commented on SUREFIRE-1216:
--
Github user justinharringa commented on the issue:
https://github.com/apache/maven-surefire/pull/110
@Tibor17 I'm also broken on this.
> TEST-*.xml files generated by Surefire are invalid
> --
>
> Key: SUREFIRE-1216
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1216
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Mirko Friedenhagen
>Assignee: Mirko Friedenhagen
> Fix For: 2.19.2
>
>
> See SUREFIRE-964 as well. The XML produced is invalid because
> {{schemaLocation}} *must* include two URIs, as outlined in
> [xmlschema-1|http://www.w3.org/TR/xmlschema-1/#schema-loc].
> Because of this, the Xerces parser fails in the Jenkins XUnit plugin and e.g.
> IntelliJ is not able to parse the file correctly.
> Suggested solution is to replace {{xsi:schemaLocation}} by
> {{xsi:noNamespaceSchemaLocation}}, which fixes this for the Unit plugin as
> well the file is parseable by IntelliJ.
--
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=15431912#comment-15431912
]
Tibor Digana commented on SUREFIRE-1245:
[~hemanth.BS]
Do you have time for this issue?
What about first of all fix the timeout problem connecting to remote browser
and then surefire.
See {{java.net.SocketException: Bad file descriptor}}. This happens when socket
is closed. Any idea what could close it?
See this article
http://stackoverflow.com/questions/9731291/how-to-set-selenium-webdriver-get-timeout
It is mentioned that the load can be blocked for very long time. Did you try to
setup implicit/explicit timeout?
> 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
>
>
[jira] [Commented] (SUREFIRE-1250) Regex testcase filtering: exception when hashmark is regex-quoted
[
https://issues.apache.org/jira/browse/SUREFIRE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431848#comment-15431848
]
Hudson commented on SUREFIRE-1250:
--
SUCCESS: Integrated in Jenkins build maven-surefire #1600 (See
[https://builds.apache.org/job/maven-surefire/1600/])
[SUREFIRE-1250] Regex testcase filtering: exception when hashmark is (tibor17:
rev 52681e56db036fa7f648ac43c084ac9f0747213e)
* (edit)
surefire-api/src/test/java/org/apache/maven/surefire/testset/TestListResolverTest.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/testset/ResolvedTest.java
> Regex testcase filtering: exception when hashmark is regex-quoted
> -
>
> Key: SUREFIRE-1250
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1250
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Zoltan Haindrich
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 2.19.2
>
> Attachments: SUREFIRE-1250.patch
>
>
> i've been using regex to select which tests to run...and i've got some wierd
> exceptions when executing
> {code}
> mvn test "-Dtest=%regex[.*\Q#\E.*]"
> {code}
> executing the above command results in:
> {code}
> java.util.regex.PatternSyntaxException:
> Illegal/unsupported escape sequence near index 1
> \E.*
> ^
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}
> i noticed earlier that maven might do some black-magic with these regexps in
> the background ( i know that it should know the class name earlier; to avoid
> starting testcases which will get entirely excluded...and thats cool )
> ...so..i assume maven does split the regex by the {{#}}; and that's okay - if
> that can't be avoided; place some pointers in the documentation about it
> and/or a more descriptive exception could be useful
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1250) Regex testcase filtering: exception when hashmark is regex-quoted
[
https://issues.apache.org/jira/browse/SUREFIRE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1250:
---
Fix Version/s: 2.19.2
> Regex testcase filtering: exception when hashmark is regex-quoted
> -
>
> Key: SUREFIRE-1250
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1250
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Zoltan Haindrich
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 2.19.2
>
> Attachments: SUREFIRE-1250.patch
>
>
> i've been using regex to select which tests to run...and i've got some wierd
> exceptions when executing
> {code}
> mvn test "-Dtest=%regex[.*\Q#\E.*]"
> {code}
> executing the above command results in:
> {code}
> java.util.regex.PatternSyntaxException:
> Illegal/unsupported escape sequence near index 1
> \E.*
> ^
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}
> i noticed earlier that maven might do some black-magic with these regexps in
> the background ( i know that it should know the class name earlier; to avoid
> starting testcases which will get entirely excluded...and thats cool )
> ...so..i assume maven does split the regex by the {{#}}; and that's okay - if
> that can't be avoided; place some pointers in the documentation about it
> and/or a more descriptive exception could be useful
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1250) Regex testcase filtering: exception when hashmark is regex-quoted
[
https://issues.apache.org/jira/browse/SUREFIRE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1250.
--
Resolution: Fixed
commit 52681e56db036fa7f648ac43c084ac9f0747213e
> Regex testcase filtering: exception when hashmark is regex-quoted
> -
>
> Key: SUREFIRE-1250
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1250
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Zoltan Haindrich
>Assignee: Tibor Digana
>Priority: Minor
> Attachments: SUREFIRE-1250.patch
>
>
> i've been using regex to select which tests to run...and i've got some wierd
> exceptions when executing
> {code}
> mvn test "-Dtest=%regex[.*\Q#\E.*]"
> {code}
> executing the above command results in:
> {code}
> java.util.regex.PatternSyntaxException:
> Illegal/unsupported escape sequence near index 1
> \E.*
> ^
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}
> i noticed earlier that maven might do some black-magic with these regexps in
> the background ( i know that it should know the class name earlier; to avoid
> starting testcases which will get entirely excluded...and thats cool )
> ...so..i assume maven does split the regex by the {{#}}; and that's okay - if
> that can't be avoided; place some pointers in the documentation about it
> and/or a more descriptive exception could be useful
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1250) Regex testcase filtering: exception when hashmark is regex-quoted
[
https://issues.apache.org/jira/browse/SUREFIRE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431783#comment-15431783
]
ASF GitHub Bot commented on SUREFIRE-1250:
--
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/113
@kgyrtkirk Please close the PR. The code was merged with master. Thx for
contributing!
> Regex testcase filtering: exception when hashmark is regex-quoted
> -
>
> Key: SUREFIRE-1250
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1250
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Zoltan Haindrich
>Assignee: Tibor Digana
>Priority: Minor
> Attachments: SUREFIRE-1250.patch
>
>
> i've been using regex to select which tests to run...and i've got some wierd
> exceptions when executing
> {code}
> mvn test "-Dtest=%regex[.*\Q#\E.*]"
> {code}
> executing the above command results in:
> {code}
> java.util.regex.PatternSyntaxException:
> Illegal/unsupported escape sequence near index 1
> \E.*
> ^
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}
> i noticed earlier that maven might do some black-magic with these regexps in
> the background ( i know that it should know the class name earlier; to avoid
> starting testcases which will get entirely excluded...and thats cool )
> ...so..i assume maven does split the regex by the {{#}}; and that's okay - if
> that can't be avoided; place some pointers in the documentation about it
> and/or a more descriptive exception could be useful
--
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=15431693#comment-15431693
]
Tibor Digana commented on SUREFIRE-1276:
{{String#isEmpty()}} is available since of Java 1.6 and we compile code with
1.5.
The point of {{countNewLines == 1 && !msg.trim().endsWith( "\n" )}} is to print
{{java.lang.IllegalArgumentException: Message}}
instead of
{{java.lang.IllegalArgumentException:
Message}}
if you call {{throw new IllegalArgumentException("Message\n");}}
The point of Groovy fix is to align expression and value.
The code {{countNewLines == 1 && !msg.trim().endsWith( "\n" )}} avoids
situation with {{throw new IllegalArgumentException("Message\n");}} without
unnecessary call {{.isEmpty()}} and without cutting msg with tokenizer.
> 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] [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
]
Gili updated SUREFIRE-1276:
---
Summary: Document handling of multiline exception messages (was:
trimStackTrace trims newlines in exception message)
> 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-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431635#comment-15431635
]
Gili commented on SUREFIRE-1276:
[~tibor17] Will do. On a side-note, don't you find the conditional of
https://github.com/apache/maven-surefire/commit/6e5fb5695a48ad072cc354e31b8fd82656b9d320#diff-fa9299aa9dbda1fe1c3f400814d2b25fR142
a bit confusing? I would recommend adding brackets to clarify the operator
ordering. Also, its not clear when {{!msg.trim().endsWith( "\n" )}} would ever
return true. I'm guessing that replacing that with {{!msg.trim().isEmpty()}}
would result in the same behavior but be more readable.
> trimStackTrace trims newlines in exception message
> --
>
> 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] [Comment Edited] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430876#comment-15430876 ] James Wen edited comment on MCOMPILER-274 at 8/22/16 9:03 PM: -- It might be worth noting that for our situation, this build process was working when we were on openjdk-7-jdk `7u111-2.6.7-0ubuntu0.14.04.2`. When openjdk-7-jdk `7u111-2.6.7-0ubuntu0.14.04.3` was [released on August 11th](http://changelogs.ubuntu.com/changelogs/pool/main/o/openjdk-7/openjdk-7_7u111-2.6.7-0ubuntu0.14.04.3/changelog), our build process automatically started using this (because we use apt-get install) and the build started failing. was (Author: rochesterinnyc): It might be worth noting that for our situation, this build process was working when we were on openjdk-7-jdk `7u111-2.6.7-0ubuntu0.14.04.2`. When openjdk-7-jdk `7u111-2.6.7-0ubuntu0.14.04.3` was [released on August 11th](http://changelogs.ubuntu.com/changelogs/pool/main/o/openjdk-7/openjdk-7_7u111-2.6.7-0ubuntu0.14.04.3/changelog), our build process automatically starting using this (because we use apt-get install) and the build started failing. > "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] (SUREFIRE-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1276:
---
Labels: documentation (was: )
> trimStackTrace trims newlines in exception message
> --
>
> 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-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431611#comment-15431611
]
Tibor Digana commented on SUREFIRE-1276:
Feel free to add a documentation.
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
> 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] [Assigned] (SUREFIRE-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1276:
--
Assignee: Tibor Digana
> trimStackTrace trims newlines in exception message
> --
>
> 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-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431609#comment-15431609
]
Gili commented on SUREFIRE-1276:
[~tibor17] Please ignore my shortened testcase (the one with "Message"). I
shortened it at the last minute and never actually testing it locally. I know
that with a longer string that contains {{\n}} I see the same behavior you
mentioned. So yes, I believe we are in agreement.
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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] [Comment Edited] (SUREFIRE-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431601#comment-15431601
]
Tibor Digana edited comment on SUREFIRE-1276 at 8/22/16 8:51 PM:
-
[~cowwoc]
Something is wrong on your side because I have expected result and the newline
is added only if the message has {{\n}} character:
{code:java}
result.append( t.getClass().getName() );
String msg = t.getMessage();
if ( msg != null )
{
result.append( ": " );
if ( isMultiLine( msg ) )
{
// SUREFIRE-986
result.append( '\n' );
}
result.append( msg );
}
{code}
Check your CLI window, maybe it's cutting the lines.
{quote}
Running ATest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 s - in
ATest
Running SomeTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<<
FAILURE! - in SomeTest
test(SomeTest) Time elapsed: 0.001 s <<< ERROR!
java.lang.IllegalArgumentException: Message
at SomeTest.test(SomeTest.java:9)
Results:
Tests in error:
SomeTest.test:9 IllegalArgument Message
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
{quote}
was (Author: tibor17):
[~cowwoc]
Something is wrong on your side because I have expected result and the newline
is added only if the message has {{\n}} character:
{code:java}
result.append( t.getClass().getName() );
String msg = t.getMessage();
if ( msg != null )
{
result.append( ": " );
if ( isMultiLine( msg ) )
{
// SUREFIRE-986
result.append( '\n' );
}
result.append( msg );
}
{code}
Check your CLI window, maybe it's cutting the lines.
{{Running ATest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 s - in
ATest
Running SomeTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<<
FAILURE! - in SomeTest
test(SomeTest) Time elapsed: 0.001 s <<< ERROR!
java.lang.IllegalArgumentException: Message
at SomeTest.test(SomeTest.java:9)
Results:
Tests in error:
SomeTest.test:9 IllegalArgument Message
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0}}
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431601#comment-15431601
]
Tibor Digana commented on SUREFIRE-1276:
[~cowwoc]
Something is wrong on your side because I have expected result and the newline
is added only if the message has {{\n}} character:
{code:java}
result.append( t.getClass().getName() );
String msg = t.getMessage();
if ( msg != null )
{
result.append( ": " );
if ( isMultiLine( msg ) )
{
// SUREFIRE-986
result.append( '\n' );
}
result.append( msg );
}
{code}
Check your CLI window, maybe it's cutting the lines.
{{Running ATest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 s - in
ATest
Running SomeTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<<
FAILURE! - in SomeTest
test(SomeTest) Time elapsed: 0.001 s <<< ERROR!
java.lang.IllegalArgumentException: Message
at SomeTest.test(SomeTest.java:9)
Results:
Tests in error:
SomeTest.test:9 IllegalArgument Message
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0}}
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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] [Comment Edited] (SUREFIRE-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431582#comment-15431582
]
Gili edited comment on SUREFIRE-1276 at 8/22/16 8:40 PM:
-
[~tibor17] If understand the code correctly, when the exception message spans
multiple lines, Surefire inserts a leading newline character to make sure that
the text is aligned. If so, this is a good idea, but should be documented as
you mentioned. If you confirm my understanding, I will try producing a PR for
this.
was (Author: cowwoc):
[~tibor17] I understand the code correctly, when the exception message spans
multiple lines, Surefire inserts a leading newline character to make sure that
the text is aligned. If so, this is a good idea, but should be documented as
you mentioned. If you confirm my understanding, I will try producing a PR for
this.
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431580#comment-15431580
]
Tibor Digana commented on SUREFIRE-1276:
no need to run the POM, I see the code talks the same language as your
experiences.
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431582#comment-15431582
]
Gili commented on SUREFIRE-1276:
[~tibor17] I understand the code correctly, when the exception message spans
multiple lines, Surefire inserts a leading newline character to make sure that
the text is aligned. If so, this is a good idea, but should be documented as
you mentioned. If you confirm my understanding, I will try producing a PR for
this.
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431572#comment-15431572
]
Tibor Digana commented on SUREFIRE-1276:
[~cowwoc]
If we need to have improvements added to our documentation according to your
expectations, feel free to open PR in GitHub.
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431563#comment-15431563
]
Tibor Digana commented on SUREFIRE-1276:
it's because of SUREFIRE-986
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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] (MSHARED-579) Upgrade to plexus-archiver 3.4
[ https://issues.apache.org/jira/browse/MSHARED-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431554#comment-15431554 ] Hudson commented on MSHARED-579: SUCCESS: Integrated in Jenkins build maven-shared #2849 (See [https://builds.apache.org/job/maven-shared/2849/]) [MSHARED-579] Upgrade to plexus-archiver 3.4 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1757265]) * (edit) maven-archiver/pom.xml > Upgrade to plexus-archiver 3.4 > -- > > Key: MSHARED-579 > URL: https://issues.apache.org/jira/browse/MSHARED-579 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-archiver-3.1.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHARED-578) Upgrade maven-shared-utils to 3.1.0
[ https://issues.apache.org/jira/browse/MSHARED-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431555#comment-15431555 ] Hudson commented on MSHARED-578: SUCCESS: Integrated in Jenkins build maven-shared #2849 (See [https://builds.apache.org/job/maven-shared/2849/]) [MSHARED-578] Upgrade maven-shared-utils to 3.1.0 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1757264]) * (edit) maven-archiver/pom.xml > Upgrade maven-shared-utils to 3.1.0 > --- > > Key: MSHARED-578 > URL: https://issues.apache.org/jira/browse/MSHARED-578 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-archiver-3.1.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431526#comment-15431526
]
Gili commented on SUREFIRE-1276:
Confirmed. Surefire 2.12.4 trims newlines in exception messages but 2.19.1 does
not. So that bug is fixed.
The second problem, which is unaffected by the value of {{}},
can be reproduced in version 2.19.1 as follows:
Run a unit test containing:
{code}
@Test
public void test()
{
throw new IllegalArgumentException("Message");
}
{code}
You will get the following output:
{code}
java.lang.IllegalArgumentException:
Message
{code}
However, if you catch the exception inside the test method and invoke
{{printStackTrace()}} then the output will be:
{code}
java.lang.IllegalArgumentException: Message
{code}
Let me know if you can reproduce this. Otherwise I will create a project as you
requested.
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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] [Comment Edited] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430867#comment-15430867 ] James Wen edited comment on MCOMPILER-274 at 8/22/16 8:14 PM: -- Hi, we're the Cloud Foundry Buildpacks team and we've encountered this issue (with almost the exact same error trace at the end as the original submitter) as well. We encountered it while trying to use our binary builder tool (https://github.com/cloudfoundry/binary-builder) to build jruby 9.1.2.0. It uses maven `3.3.9`, ant `1.9.7`, and openjdk-7 from the trusty ubuntu apt repo (version `7u111-2.6.7-0ubuntu0.14.04.3`). It will try to install openjdk via apt-get, build and compile ant and maven, and then use maven to try to build jruby. Reproduction: ``` git clone g...@github.com:cloudfoundry/binary-builder.git cd binary-builder docker run -it -v $(pwd):/binary-builder cloudfoundry/cflinuxfs2 bash cd /binary-builder ./bin/binary-builder --name=jruby --version=9.1.2.0_ruby-2.3.0 --sha256=dfd44f532105725a4d4a2378a3b6a06899bae660be21538a5b36b41e4dd045e6 ``` The full error log after switching maven to try and build jruby with the `-X` flag enabled is here: https://gist.github.com/RochesterinNYC/fac1f36bb98ded1f5a135f10b2c8741c was (Author: rochesterinnyc): Hi, we're the Cloud Foundry Buildpacks team and we've encountered this issue (with almost the exact same error trace at the end as the original submitter) as well. We encountered it while trying to use our binary builder tool (https://github.com/cloudfoundry/binary-builder) to build jruby 9.1.2.0. It uses maven `3.3.9`, ant `1.9.7`, and openjdk-7 from the trusty ubuntu apt repo (version `7u111-2.6.7-0ubuntu0.14.04.3`). It will try to install openjdk via apt-get, build and compile ant and maven, and then use maven to try to build jruby. Reproduction: ``` git clone g...@github.com:cloudfoundry/binary-builder.git cd binary-builder docker run -it -v $(pwd):/binary-builder bash cd /binary-builder ./bin/binary-builder --name=jruby --version=9.1.2.0_ruby-2.3.0 --sha256=dfd44f532105725a4d4a2378a3b6a06899bae660be21538a5b36b41e4dd045e6 ``` The full error log after switching maven to try and build jruby with the `-X` flag enabled is here: https://gist.github.com/RochesterinNYC/fac1f36bb98ded1f5a135f10b2c8741c > "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] [Closed] (MSHARED-579) Upgrade to plexus-archiver 3.4
[ https://issues.apache.org/jira/browse/MSHARED-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-579. --- Resolution: Fixed Done in [r1757265|https://svn.apache.org/r1757265] > Upgrade to plexus-archiver 3.4 > -- > > Key: MSHARED-579 > URL: https://issues.apache.org/jira/browse/MSHARED-579 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-archiver-3.1.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHARED-579) Upgrade to plexus-archiver 3.4
Karl Heinz Marbaise created MSHARED-579: --- Summary: Upgrade to plexus-archiver 3.4 Key: MSHARED-579 URL: https://issues.apache.org/jira/browse/MSHARED-579 Project: Maven Shared Components Issue Type: Improvement Components: maven-archiver Affects Versions: maven-archiver-3.1.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: maven-archiver-3.1.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSHARED-578) Upgrade maven-shared-utils to 3.1.0
[ https://issues.apache.org/jira/browse/MSHARED-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-578. --- Resolution: Fixed Done in [r1757264|https://svn.apache.org/r1757264] > Upgrade maven-shared-utils to 3.1.0 > --- > > Key: MSHARED-578 > URL: https://issues.apache.org/jira/browse/MSHARED-578 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-archiver-3.1.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHARED-578) Upgrade maven-shared-utils to 3.1.0
Karl Heinz Marbaise created MSHARED-578: --- Summary: Upgrade maven-shared-utils to 3.1.0 Key: MSHARED-578 URL: https://issues.apache.org/jira/browse/MSHARED-578 Project: Maven Shared Components Issue Type: Improvement Components: maven-archiver Affects Versions: maven-archiver-3.1.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: maven-archiver-3.1.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MWAR-384) failOnMissingWebXml flag ignored if parent pom defined.
[ https://issues.apache.org/jira/browse/MWAR-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431508#comment-15431508 ] Karl Heinz Marbaise commented on MWAR-384: -- Do you have an example project which shows the behaviour? > failOnMissingWebXml flag ignored if parent pom defined. > --- > > Key: MWAR-384 > URL: https://issues.apache.org/jira/browse/MWAR-384 > Project: Maven WAR Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: Linux x86_64 CentOS 6 >Reporter: Paweł Ryszawa > Labels: maven > > false does not work as expected if > the pom.xml relates to some parent pom, i.e has section. No matter > what the parent pom contains, even if it is almost empty, maven-war-plugin > fails. On commenting out the parent relationship in the pom, the flag is seen > working again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1262) Add modulepath support
[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431499#comment-15431499
]
Robert Scholte commented on SUREFIRE-1262:
--
AFAIK this option has always been there.
Just installed Java 1.5, got this output:
{noformat}
>"c:\Program Files (x86)\Java\jdk1.5.0_15\bin\java.exe" -version
java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Client VM (build 1.5.0_15-b04, mixed mode, sharing)
{noformat}
m-javadoc-p has a unittest for this to detect all kinds of output from
different vendors
> Add modulepath support
> --
>
> Key: SUREFIRE-1262
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1262
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> With the Jigsaw project Java9 is extended with a modulepath. This means that
> surefire should be executed in a different way.
> When working with a modulepath, the Classpath in the MANIFEST of the
> executable jar will be ignored, you need need to add everything on
> commandline.
> Just like javadoc, the java executable has an {{@}} option, where you
> can add arguments per line. So this is the new preferred way to build the
> module-path.
> IIUC for surefire it is important to add {{-Xpatch target/test-classes}}
> which makes it possible to use the same packages as target/classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431491#comment-15431491
]
Tibor Digana commented on SUREFIRE-1276:
[~cowwoc]
Trim means that stack trace entry is printed if the class is your test. It has
nothing to do with exception message; otherwise the issue is not clear to me.
Can you attach a project?
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431485#comment-15431485
]
Tibor Digana commented on SUREFIRE-1276:
If the message contains \n new line is printed which is a fix in some of the
last version(s).
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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-1275) Test regex patterns should be cached
[ https://issues.apache.org/jira/browse/SUREFIRE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431449#comment-15431449 ] Hudson commented on SUREFIRE-1275: -- UNSTABLE: Integrated in Jenkins build maven-surefire #1596 (See [https://builds.apache.org/job/maven-surefire/1596/]) [SUREFIRE-1275] Test regex patterns should be cached (tibor17: rev 02d665cef290fb5ba02169367e4bc2e2a8f494f7) * (edit) surefire-api/src/test/java/org/apache/maven/surefire/testset/TestListResolverTest.java * (edit) surefire-providers/common-junit48/src/test/java/org/apache/maven/surefire/common/junit48/FilterFactoryTest.java * (edit) surefire-api/src/main/java/org/apache/maven/surefire/testset/TestListResolver.java * (edit) surefire-api/src/main/java/org/apache/maven/surefire/testset/ResolvedTest.java > Test regex patterns should be cached > > > Key: SUREFIRE-1275 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1275 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.19 >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > > This should improve performance a bit for parameters test/includes/excludes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431448#comment-15431448
]
Hudson commented on SUREFIRE-1274:
--
UNSTABLE: Integrated in Jenkins build maven-surefire #1596 (See
[https://builds.apache.org/job/maven-surefire/1596/])
[SUREFIRE-1274] reverted c9b0914116cb49fb082ffa7d3af0ce0314f8fbc1 (tibor17: rev
4ad2e4c11f0a9e1309841292c69b81d3f34e95bb)
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/IsolatedClassLoader.java
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1276) trimStackTrace trims newlines in exception message
[
https://issues.apache.org/jira/browse/SUREFIRE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431444#comment-15431444
]
Gili commented on SUREFIRE-1276:
I just noticed a second related problem. Even with {{}}
disabled, Surefire is translating:
{code}
java.lang.IllegalArgumentException: some message
{code}
into
{code}
java.lang.IllegalArgumentException:
some message
{code}
Meaning, it is adding a newline before the exception message. Again this
behavior is undocumented and there is no obvious way to disable it.
> trimStackTrace trims newlines in exception message
> --
>
> Key: SUREFIRE-1276
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Gili
>
> 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] [Created] (SUREFIRE-1276) trimStackTrace trims newlines in exception message
Gili created SUREFIRE-1276:
--
Summary: trimStackTrace trims newlines in exception message
Key: SUREFIRE-1276
URL: https://issues.apache.org/jira/browse/SUREFIRE-1276
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Reporter: Gili
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] [Closed] (SUREFIRE-1275) Test regex patterns should be cached
[ https://issues.apache.org/jira/browse/SUREFIRE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1275. -- Resolution: Fixed commit 02d665cef290fb5ba02169367e4bc2e2a8f494f7 > Test regex patterns should be cached > > > Key: SUREFIRE-1275 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1275 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.19 >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > > This should improve performance a bit for parameters test/includes/excludes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1262) Add modulepath support
[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431354#comment-15431354
]
Tibor Digana commented on SUREFIRE-1262:
Is the first line returned by {{java -version}} under Java Spec (don't mean
only OpenJDK 9) since of Java 1.5 ?
How about other JRE vendors are handling this command?
> Add modulepath support
> --
>
> Key: SUREFIRE-1262
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1262
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> With the Jigsaw project Java9 is extended with a modulepath. This means that
> surefire should be executed in a different way.
> When working with a modulepath, the Classpath in the MANIFEST of the
> executable jar will be ignored, you need need to add everything on
> commandline.
> Just like javadoc, the java executable has an {{@}} option, where you
> can add arguments per line. So this is the new preferred way to build the
> module-path.
> IIUC for surefire it is important to add {{-Xpatch target/test-classes}}
> which makes it possible to use the same packages as target/classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431337#comment-15431337 ] Robert Scholte commented on MCOMPILER-274: -- https://github.com/codehaus-plexus/plexus-compiler/issues/16 and https://github.com/codehaus-plexus/plexus-compiler/issues/15 contain the related fixes. > "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] [Issue Comment Deleted] (SUREFIRE-1272) Create better report for AssumptionFailure
[
https://issues.apache.org/jira/browse/SUREFIRE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1272:
---
Comment: was deleted
(was: [~ema]
We have low test coverage in project. Please add a test in
{{maven-surefire-report-plugin/src/test/java/../}}. It's easy, just see how we
write the tests and see {{src/test/resources}}. Thx for help.)
> Create better report for AssumptionFailure
> --
>
> Key: SUREFIRE-1272
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1272
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Junit 4.x support
>Reporter: Jim Ma
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SUREFIRE-1275) Test regex patterns should be cached
Tibor Digana created SUREFIRE-1275: -- Summary: Test regex patterns should be cached Key: SUREFIRE-1275 URL: https://issues.apache.org/jira/browse/SUREFIRE-1275 Project: Maven Surefire Issue Type: Improvement Components: Maven Failsafe Plugin, Maven Surefire Plugin Affects Versions: 2.19 Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19.2 This should improve performance a bit for parameters test/includes/excludes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431163#comment-15431163
]
Jodi commented on SUREFIRE-1274:
Hi, correct method seems to be to remove ${argLine}, thanks for clarifying risk
with forkCount=0 impact to me and others
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431158#comment-15431158
]
Tibor Digana commented on SUREFIRE-1274:
Don't use {{forkCount=0}} otherwise you are not able to start Java agent; means
jacoco.
Keep using default {{forkCount}} or obsolete parameter {{forkMode}} or higher
than 1.
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1262) Add modulepath support
[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431152#comment-15431152
]
Robert Scholte commented on SUREFIRE-1262:
--
Toolchain doesn't detect the java version, it simply picks the one selected.
In case of non-fork I would check the existence of
[java.lang.reflect.Module|http://cr.openjdk.java.net/~mr/jigsaw/spec/api/java/lang/reflect/Module.html].
For forked you need to call {{java -version}} and read the first line, analyze
its value based on http://openjdk.java.net/jeps/223
> Add modulepath support
> --
>
> Key: SUREFIRE-1262
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1262
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> With the Jigsaw project Java9 is extended with a modulepath. This means that
> surefire should be executed in a different way.
> When working with a modulepath, the Classpath in the MANIFEST of the
> executable jar will be ignored, you need need to add everything on
> commandline.
> Just like javadoc, the java executable has an {{@}} option, where you
> can add arguments per line. So this is the new preferred way to build the
> module-path.
> IIUC for surefire it is important to add {{-Xpatch target/test-classes}}
> which makes it possible to use the same packages as target/classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431121#comment-15431121
]
Jodi commented on SUREFIRE-1274:
It seems that you might be able to remove ${argLine} completely when within a
profile.
This setting was a solution on stack-exchange for problems with JaCoCo and
surefire integration, but I cannot remember the specific problem it solved
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds
[ https://issues.apache.org/jira/browse/SUREFIRE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431113#comment-15431113 ] Robert Scholte commented on SUREFIRE-1265: -- I think we should try to revert this. Michael said the issue is somewhere else. If that fixes his issue, then no need to keep this change. I would expect that the SystemClassloader is indeed we want. > reuseForks=false fails on jdk-9-ea builds > - > > Key: SUREFIRE-1265 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1265 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Michael Musgrove >Assignee: Tibor Digana > Labels: jigsaw > Attachments: j9test.tar > > > When I run any surefire test (with reuseForks=false) that uses java.sql > classes on recent jdk-9 ea builds it fails with: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project maven-surefire-plugin-example: Execution default-test of goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: > java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException > -> [Help 1] > If I run it with reuseForks=true it works fine. > This problem was introduced in jdk build 9-ea+122 > (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw > team addressed: > d20279be77d9 8154189 Deprivilege java.sql and java.sql.rowset module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431114#comment-15431114
]
Jodi commented on SUREFIRE-1274:
I'm guessing this one is useful too if fork=0 is a problem
http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPLUGIN-311) Goal "plugin:report": System Requirements -> Minimum Maven version is not correctly extracted from effective pom
[
https://issues.apache.org/jira/browse/MPLUGIN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431109#comment-15431109
]
Konrad Windszus commented on MPLUGIN-311:
-
Actually it works as expected because the {{prerequisites}} section is not
supposed to be inherited (https://maven.apache.org/pom.html#Inheritance).
> Goal "plugin:report": System Requirements -> Minimum Maven version is not
> correctly extracted from effective pom
>
>
> Key: MPLUGIN-311
> URL: https://issues.apache.org/jira/browse/MPLUGIN-311
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 3.4
>Reporter: Konrad Windszus
>
> Currently the minimum Maven version being exposed in {{plugin-info.html}}
> through the goal {{report}} only seems to be extracted from the current
> {{prerequisites->maven}} element in the current pom.xml. In case this is set
> in some parent pom, it falls back to the default of version {{2.0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431112#comment-15431112
]
Jodi commented on SUREFIRE-1274:
Switching on forking may cause an issue related to this thread:
https://issues.apache.org/jira/browse/SUREFIRE-335
I don't know if this is what you are trying to explain with regards to maven
being the ultimate cause
when forking is disabled this is one message which jumps out regarding the
classparth ${argLine} error
[WARNING] useSystemClassloader setting has no effect when not forking
I don't know the internals of surefire or maven so I'll leave this as resolve
with forking disabled when inside profiles
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (MPLUGIN-311) Goal "plugin:report": System Requirements -> Minimum Maven version is not correctly extracted from effective pom
[
https://issues.apache.org/jira/browse/MPLUGIN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved MPLUGIN-311.
-
Resolution: Invalid
> Goal "plugin:report": System Requirements -> Minimum Maven version is not
> correctly extracted from effective pom
>
>
> Key: MPLUGIN-311
> URL: https://issues.apache.org/jira/browse/MPLUGIN-311
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 3.4
>Reporter: Konrad Windszus
>
> Currently the minimum Maven version being exposed in {{plugin-info.html}}
> through the goal {{report}} only seems to be extracted from the current
> {{prerequisites->maven}} element in the current pom.xml. In case this is set
> in some parent pom, it falls back to the default of version {{2.0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jodi updated SUREFIRE-1273: --- Attachment: pom-with-profile-working.xml Added working pom with profile containing JaCoCo and surefire (set forks to 0 for execution of single tests inside a profile) #1274 > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi >Assignee: Tibor Digana > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom-with-profile-working.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jodi updated SUREFIRE-1273: --- Attachment: (was: pom.xml) > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi >Assignee: Tibor Digana > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jodi updated SUREFIRE-1273: --- Attachment: pom.xml Working pom example for profiles and surefire/JaCoCo > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi >Assignee: Tibor Digana > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPLUGIN-311) Goal "plugin:report": System Requirements -> Minimum Maven version is not correctly extracted from effective pom
[
https://issues.apache.org/jira/browse/MPLUGIN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431073#comment-15431073
]
Konrad Windszus commented on MPLUGIN-311:
-
The issue seems to be in
https://github.com/apache/maven-plugin-tools/blob/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java#L672.
> Goal "plugin:report": System Requirements -> Minimum Maven version is not
> correctly extracted from effective pom
>
>
> Key: MPLUGIN-311
> URL: https://issues.apache.org/jira/browse/MPLUGIN-311
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 3.4
>Reporter: Konrad Windszus
>
> Currently the minimum Maven version being exposed in {{plugin-info.html}}
> through the goal {{report}} only seems to be extracted from the current
> {{prerequisites->maven}} element in the current pom.xml. In case this is set
> in some parent pom, it falls back to the default of version {{2.0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MPLUGIN-311) Goal "plugin:report": System Requirements -> Minimum Maven version is not correctly extracted from effective pom
[
https://issues.apache.org/jira/browse/MPLUGIN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated MPLUGIN-311:
Description: Currently the minimum Maven version being exposed in
{{plugin-info.html}} through the goal {{report}} only seems to be extracted
from the current {{prerequisites->maven}} element in the current pom.xml. In
case this is set in some parent pom, it falls back to the default of version
{{2.0}}. (was: Currently the minimum Maven version only seems to be extracted
from the current {{prerequisites->maven}} element in the current pom.xml. In
case this is set in some parent pom, it falls back to the default of version
{{2.0}}.)
> Goal "plugin:report": System Requirements -> Minimum Maven version is not
> correctly extracted from effective pom
>
>
> Key: MPLUGIN-311
> URL: https://issues.apache.org/jira/browse/MPLUGIN-311
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 3.4
>Reporter: Konrad Windszus
>
> Currently the minimum Maven version being exposed in {{plugin-info.html}}
> through the goal {{report}} only seems to be extracted from the current
> {{prerequisites->maven}} element in the current pom.xml. In case this is set
> in some parent pom, it falls back to the default of version {{2.0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431068#comment-15431068 ] Jodi commented on SUREFIRE-1273: Hi, thanks, the changes to the pom do seem to have resolved the case of mvn:build completely inside the profile tag. I appreciate the time you've spent on this ticket The issue with #1274 is still happening but I'll clean up the pom and post an working version shortly for this #1273 for other users > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi >Assignee: Tibor Digana > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MPLUGIN-311) Goal "plugin:report": System Requirements -> Minimum Maven version is not correctly extracted from effective pom
[
https://issues.apache.org/jira/browse/MPLUGIN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated MPLUGIN-311:
Summary: Goal "plugin:report": System Requirements -> Minimum Maven version
is not correctly extracted from effective pom (was: System Requirements:
Minimum Maven version is not correctly extracted from effective pom)
> Goal "plugin:report": System Requirements -> Minimum Maven version is not
> correctly extracted from effective pom
>
>
> Key: MPLUGIN-311
> URL: https://issues.apache.org/jira/browse/MPLUGIN-311
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 3.4
>Reporter: Konrad Windszus
>
> Currently the minimum Maven version only seems to be extracted from the
> current {{prerequisites->maven}} element in the current pom.xml. In case this
> is set in some parent pom, it falls back to the default of version {{2.0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MPLUGIN-311) System Requirements: Minimum Maven version is not correctly extracted from effective pom
Konrad Windszus created MPLUGIN-311:
---
Summary: System Requirements: Minimum Maven version is not
correctly extracted from effective pom
Key: MPLUGIN-311
URL: https://issues.apache.org/jira/browse/MPLUGIN-311
Project: Maven Plugin Tools
Issue Type: Improvement
Components: Plugin Plugin
Affects Versions: 3.4
Reporter: Konrad Windszus
Currently the minimum Maven version only seems to be extracted from the current
{{prerequisites->maven}} element in the current pom.xml. In case this is set in
some parent pom, it falls back to the default of version {{2.0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1273. -- Resolution: Not A Bug Assignee: Tibor Digana MNG issue > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi >Assignee: Tibor Digana > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430993#comment-15430993
]
Tibor Digana edited comment on SUREFIRE-1273 at 8/22/16 3:28 PM:
-
[~jodi.cur...@gmail.com]
This is definitely Maven issue, you can report it in
https://issues.apache.org/jira/browse/MNG
The problem is with difference between
{code:xml}
${argLine}
{code}
and
{code:xml}
${argLine} -Dfile.encoding=${project.build.sourceEncoding}
{code}
The Maven debug mode specifies the property
{code}${argLine}{code} in the first case and accordingly to
the second case but the problem is that the parameter in
{{AbstractSurefireMojo.java}}
is set with NULL for the first case {code}${argLine}{code}
{code:java}
@Parameter( property = "argLine" )
private String argLine;
{code}
, but the second case sets the parameter with the string as specified in POM
without any NULL treatment.
was (Author: tibor17):
[~jodi.cur...@gmail.com]
This is definitely Maven issue, you can report it in
https://issues.apache.org/jira/browse/MNG
The problem is with difference between
{code:xml}
${argLine}
{code}
and
{code:xml}
${argLine} -Dfile.encoding=${project.build.sourceEncoding}
{code}
The Maven debug mode specifies the property ${argLine} in
the first case and accordingly to the second case but the problem is that the
parameter in {{AbstractSurefireMojo.java}}
is set with NULL for the first case ${argLine}
{code:java}
@Parameter( property = "argLine" )
private String argLine;
{code}
, but the second case sets the parameter with the string as specified in POM
without any NULL treatment.
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430993#comment-15430993
]
Tibor Digana edited comment on SUREFIRE-1273 at 8/22/16 3:27 PM:
-
[~jodi.cur...@gmail.com]
This is definitely Maven issue, you can report it in
https://issues.apache.org/jira/browse/MNG
The problem is with difference between
{code:xml}
${argLine}
{code}
and
{code:xml}
${argLine} -Dfile.encoding=${project.build.sourceEncoding}
{code}
The Maven debug mode specifies the property ${argLine} in
the first case and accordingly to the second case but the problem is that the
parameter in {{AbstractSurefireMojo.java}}
is set with NULL for the first case ${argLine}
{code:java}
@Parameter( property = "argLine" )
private String argLine;
{code}
, but the second case sets the parameter with the string as specified in POM
without any NULL treatment.
was (Author: tibor17):
[~jodi.cur...@gmail.com]
This is definitely Maven issue, you can report it in
https://issues.apache.org/jira/browse/MNG
The problem is with difference between
{code:xml}
${argLine}
{code}
and
{code:xml}
${argLine} -Dfile.encoding=${project.build.sourceEncoding}
{code}
The Maven debug mode specifies the property ${argLine} in
the first case and accordingly to the second case but the problem is that the
parameter in {{AbstractSurefireMojo.java}}
is set with NULL for the first case ${argLine}
{code:java}
@Parameter( property = "argLine" )
private String argLine;
{code}
, but the second setting is set with the string as specified in POM without any
NULL treatment.
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430993#comment-15430993
]
Tibor Digana commented on SUREFIRE-1273:
[~jodi.cur...@gmail.com]
This is definitely Maven issue, you can report it in
https://issues.apache.org/jira/browse/MNG
The problem is with difference between
{code:xml}
${argLine}
{code}
and
{code:xml}
${argLine} -Dfile.encoding=${project.build.sourceEncoding}
{code}
The Maven debug mode specifies the property ${argLine} in
the first case and accordingly to the second case but the problem is that the
parameter in {{AbstractSurefireMojo.java}}
is set with NULL for the first case ${argLine}
{code:java}
@Parameter( property = "argLine" )
private String argLine;
{code}
, but the second setting is set with the string as specified in POM without any
NULL treatment.
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430987#comment-15430987 ] Grzegorz Slowikowski commented on MCOMPILER-274: Robert Scholte wrote " I've improved the parsing". I mean, maybe you can double check the parsing with different Java versions. > "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] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430962#comment-15430962 ] Jodi commented on SUREFIRE-1273: I appreciate the pom, it has no doubt made my pom and understanding better, but not everyone needs, or has a CI server to hand, and it's certainly a big ask for someone without too much experience to set something like that up from scratch as a pre-requisite for doing any kind of code-coverage. Unfortunately the changes have the same outcome, changing the fork number to a number other than 0 from execution within a profile - causes a high percentage direct single test executions to fail (perhaps close to 100%) (ticket #1274 and occasional failures ticket #1273) Thanks for helping me understand maven and surefire a bit better though. > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430938#comment-15430938 ] James Wen commented on MCOMPILER-274: - I'm not sure what you're suggesting here [~gslowikowski] ? > "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
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430924#comment-15430924 ] Grzegorz Slowikowski commented on MCOMPILER-274: Oracle Javac error/warning message format changed between Java 1.6 and 1.7. I don't remember details. Check Java version when analyzing messages. > "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] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430921#comment-15430921 ] Tibor Digana commented on SUREFIRE-1273: In normal circumstances the developer does not run JaCoCo. > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430917#comment-15430917
]
Tibor Digana commented on SUREFIRE-1273:
We use Jenkins, therefore such profile.
The plugin management specifies versions.
build/plugins specify all plugins and their configuration used by default build
life cycle.
The JaCoCo plugin does not specify phase.
Your POM should look like this in principle.
{code:xml}
org.jacoco
jacoco-maven-plugin
0.7.7.201606060606
maven-surefire-plugin
2.19.1
maven-surefire-plugin
jenkins
org.jacoco
jacoco-maven-plugin
jacoco-agent
prepare-agent
jacoco.agent
maven-surefire-plugin
${jacoco.agent}
{code}
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430884#comment-15430884 ] Jodi commented on SUREFIRE-1273: Setting forks to 0 seems to resolve the issue in a handful or repetitive tests. I think it may be a mistake to close the issue unless this is known or due to other external factors like maven, but it's not my project, so I guess none of my business. > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430876#comment-15430876 ] James Wen commented on MCOMPILER-274: - It might be worth noting that for our situation, this build process was working when we were on openjdk-7-jdk `7u111-2.6.7-0ubuntu0.14.04.2`. When openjdk-7-jdk `7u111-2.6.7-0ubuntu0.14.04.3` was [released on August 11th](http://changelogs.ubuntu.com/changelogs/pool/main/o/openjdk-7/openjdk-7_7u111-2.6.7-0ubuntu0.14.04.3/changelog), our build process automatically starting using this (because we use apt-get install) and the build started failing. > "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] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430877#comment-15430877
]
Jodi commented on SUREFIRE-1274:
Hi
Setting forks to 0 seems to resolve the issue in some repetitive testing so it
seems to be related to threading within a project within the hierarchy. This is
without making changes anywhere else.
Unless this threading is a problem within Maven I think closing this issue may
be a mistake
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MCOMPILER-274) "Compilation failure" message should say what actually went wrong
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430867#comment-15430867 ] James Wen edited comment on MCOMPILER-274 at 8/22/16 2:34 PM: -- Hi, we're the Cloud Foundry Buildpacks team and we've encountered this issue (with almost the exact same error trace at the end as the original submitter) as well. We encountered it while trying to use our binary builder tool (https://github.com/cloudfoundry/binary-builder) to build jruby 9.1.2.0. It uses maven `3.3.9`, ant `1.9.7`, and openjdk-7 from the trusty ubuntu apt repo (version `7u111-2.6.7-0ubuntu0.14.04.3`). It will try to install openjdk via apt-get, build and compile ant and maven, and then use maven to try to build jruby. Reproduction: ``` git clone g...@github.com:cloudfoundry/binary-builder.git cd binary-builder docker run -it -v $(pwd):/binary-builder bash cd /binary-builder ./bin/binary-builder --name=jruby --version=9.1.2.0_ruby-2.3.0 --sha256=dfd44f532105725a4d4a2378a3b6a06899bae660be21538a5b36b41e4dd045e6 ``` The full error log after switching maven to try and build jruby with the `-X` flag enabled is here: https://gist.github.com/RochesterinNYC/fac1f36bb98ded1f5a135f10b2c8741c was (Author: rochesterinnyc): Hi, we're the Cloud Foundry Buildpacks team and we've encountered this issue (with almost the exact same error trace at the end as the original submitter) as well. We encountered it while trying to use our binary builder tool (https://github.com/cloudfoundry/binary-builder) to build jruby 9.1.2.0. It uses maven `3.3.9`, ant `1.9.7`, and openjdk-7 from the trusty ubuntu apt repo (version `7u111-2.6.7-0ubuntu0.14.04.3`). It will try to install openjdk via apt-get, build and compile ant and maven, and then use maven to try to build jruby. Reproduction: ``` git clone g...@github.com:cloudfoundry/binary-builder.git cd binary-builder docker run -it -v $(pwd):/binary-builder bash cd /binary-builder ./bin/binary-builder --name=jruby --version=9.1.2.0_ruby-2.3.0 --sha256=dfd44f532105725a4d4a2378a3b6a06899bae660be21538a5b36b41e4dd045e6 ``` We've also attached the full error log after switching maven to try and build jruby with the `-X` flag enabled. > "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
[ https://issues.apache.org/jira/browse/MCOMPILER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430867#comment-15430867 ] James Wen commented on MCOMPILER-274: - Hi, we're the Cloud Foundry Buildpacks team and we've encountered this issue (with almost the exact same error trace at the end as the original submitter) as well. We encountered it while trying to use our binary builder tool (https://github.com/cloudfoundry/binary-builder) to build jruby 9.1.2.0. It uses maven `3.3.9`, ant `1.9.7`, and openjdk-7 from the trusty ubuntu apt repo (version `7u111-2.6.7-0ubuntu0.14.04.3`). It will try to install openjdk via apt-get, build and compile ant and maven, and then use maven to try to build jruby. Reproduction: ``` git clone g...@github.com:cloudfoundry/binary-builder.git cd binary-builder docker run -it -v $(pwd):/binary-builder bash cd /binary-builder ./bin/binary-builder --name=jruby --version=9.1.2.0_ruby-2.3.0 --sha256=dfd44f532105725a4d4a2378a3b6a06899bae660be21538a5b36b41e4dd045e6 ``` We've also attached the full error log after switching maven to try and build jruby with the `-X` flag enabled. > "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] [Issue Comment Deleted] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jodi updated SUREFIRE-1274:
---
Comment: was deleted
(was: Unless you can say specifically what is causing the execution not to find
the main class (or cause the perception of this) I strongly disagree that you
should dismiss this issue out of hand)
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430852#comment-15430852
]
Tibor Digana commented on SUREFIRE-1273:
[~jodi.cur...@gmail.com]
You maybe expect {code:xml}${argLine}
-Dfile.encoding=${project.build.sourceEncoding}{code}
to become {code:xml}
-Dfile.encoding=${project.build.sourceEncoding}{code}
and ${argLine} as an empty string, but this has nothing to do with surefire
nothing but another project Maven (MNG).
AFAIK this is just normal behavior in Maven and maybe controversial.
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430863#comment-15430863 ] Jodi commented on SUREFIRE-1273: OK, are you saying until I resolve this issue I need to move docker parts into a profile and leave surefire and JaCoCo tests in the main maven configuration, and that this is due to a controversial design issue within maven's community? Thanks > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jodi updated SUREFIRE-1273: --- Comment: was deleted (was: This issue seems to be highly intermittent, which is telling me there is a problem with the plugin, it wasn't happening before moving to profiles. Pointing me at the project source repository doesn't really tell me much about what I am doing wrong, it looks to me like some sort of issue related to the threading, but I don't have the experience to know for sure, but I do think dismissing it because of the error message may be a mistake unless there is a concrete cause, ie Netbeans executing the test using the wrong command line call, or some clear directive regarding setting the main class when calling a specific test (or any tests if inside the profile)) > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430860#comment-15430860
]
Jodi commented on SUREFIRE-1274:
Unless you can say specifically what is causing the execution not to find the
main class (or cause the perception of this) I strongly disagree that you
should dismiss this issue out of hand
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430857#comment-15430857
]
Jodi commented on SUREFIRE-1274:
This issue seems to be highly intermittent, which is telling me there is a
problem with the plugin, it wasn't happening before moving to profiles.
Pointing me at the project source repository doesn't really tell me much about
what I am doing wrong, it looks to me like some sort of issue related to the
threading, but I don't have the experience to know for sure, but I do think
dismissing it because of the error message may be a mistake unless there is a
concrete cause, ie Netbeans executing the test using the wrong command line
call, or some clear directive regarding setting the main class when calling a
specific test (or any tests if inside the profile)
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430856#comment-15430856 ] Jodi commented on SUREFIRE-1273: This issue seems to be highly intermittent, which is telling me there is a problem with the plugin, it wasn't happening before moving to profiles. Pointing me at the project source repository doesn't really tell me much about what I am doing wrong, it looks to me like some sort of issue related to the threading, but I don't have the experience to know for sure, but I do think dismissing it because of the error message may be a mistake unless there is a concrete cause, ie Netbeans executing the test using the wrong command line call, or some clear directive regarding setting the main class when calling a specific test (or any tests if inside the profile) > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1274.
--
Resolution: Duplicate
Assignee: Tibor Digana
the same root cause as in SUREFIRE-1273.
see the logs:
Error: Could not find or load main class \\${argLine}
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
>Assignee: Tibor Digana
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds
[ https://issues.apache.org/jira/browse/SUREFIRE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430824#comment-15430824 ] Tibor Digana commented on SUREFIRE-1265: [~rfscholte] What do you think about this change. Shall we keep it in master? https://github.com/apache/maven-surefire/commit/c9b0914116cb49fb082ffa7d3af0ce0314f8fbc1 > reuseForks=false fails on jdk-9-ea builds > - > > Key: SUREFIRE-1265 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1265 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Michael Musgrove >Assignee: Tibor Digana > Labels: jigsaw > Attachments: j9test.tar > > > When I run any surefire test (with reuseForks=false) that uses java.sql > classes on recent jdk-9 ea builds it fails with: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project maven-surefire-plugin-example: Execution default-test of goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: > java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException > -> [Help 1] > If I run it with reuseForks=true it works fine. > This problem was introduced in jdk build 9-ea+122 > (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw > team addressed: > d20279be77d9 8154189 Deprivilege java.sql and java.sql.rowset module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jodi updated SUREFIRE-1273: --- Attachment: (was: surefilre-plugin-single-test.log) > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jodi updated SUREFIRE-1273: --- Attachment: surefilre-plugin-single-test.log pom-surefire-single-test-fail.xml Added pom and test log for reproducing issue > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom-surefire-single-test-fail.xml, > pom.xml, surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430819#comment-15430819 ] Jodi commented on SUREFIRE-1273: Why should this need to be changed just for moving it into a profile? Thanks > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
[
https://issues.apache.org/jira/browse/SUREFIRE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jodi updated SUREFIRE-1274:
---
Attachment: pom-surefire-single-test-fail.xml
surefilre-plugin-single-test.log
Added log and pom file causing issue
> maven test fails when running inside a profile if executing for single class
>
>
> Key: SUREFIRE-1274
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Maven v3.0.5
> Netbeans IDE 8.1 Release
> Windows 10 Pro v6.3
> jacoco-maven-plugin 0.7.7.201606060606
> Spring Boot
>Reporter: Jodi
> Labels: newbie, test, windows
> Attachments: pom-surefire-single-test-fail.xml,
> surefilre-plugin-single-test.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, try and use jacoco-maven-plugin with
> maven-surefire-plugin while inside a profile to address as yet unknown issues
> when adding maven-docker-plugin to pom.xml
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
> 3. Setting plugin version to 2.19.1 in POM
> 4. Switching to "test" profile
> 5. Run mvn:build from Netbeans
> 6. Running mv:test on any specific class
> ##Outcome
> maven-surefire-plugin fails while Forking: Error: Could not find or load main
> class ${argLine}
> See attached error.log and pom.xml
> ##Notes
> Test fails with or without following pom.xml section commented out in plugin
> configuration
> ...
> 1
> true
>...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[ https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jodi updated SUREFIRE-1273: --- Attachment: (was: pom-surefire-single-test-fail.xml) > Adding plugin inside Maven profile breaks mvn:build on project > -- > > Key: SUREFIRE-1273 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1273 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 > Environment: Windows 10 x64 Professional version 6.3 > Netbeans 8.1 Release > Maven v3.0.5 > OracleJDKx64 v1.8.0_11 >Reporter: Jodi > Labels: newbie, windows > Attachments: pom-jacoco.xml, pom.xml, > surefire-plugin-success-jacoco.log, surefire-profiles-error.log > > > ##Conditions which led to the issue > Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin > failed to work consistently when using docker-maven-plugin, this is an issue > which is to be followed up next. > ##Maven configuration > After: > 1. Opening a project POM which hasn't yet been migrated to docker > 2. Disabling jacoco-maven-plugin > 3. Moving maven-surefire-plugin to a "test" profile > 4. Setting plugin version to 2.19.1 in POM > 5. Switching to "test" profile > 6. Run mvn:build from Netbeans > ##Outcome > maven-surefire-plugin fails during a normal build command - see attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1274) maven test fails when running inside a profile if executing for single class
Jodi created SUREFIRE-1274:
--
Summary: maven test fails when running inside a profile if
executing for single class
Key: SUREFIRE-1274
URL: https://issues.apache.org/jira/browse/SUREFIRE-1274
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.19.1
Environment: Maven v3.0.5
Netbeans IDE 8.1 Release
Windows 10 Pro v6.3
jacoco-maven-plugin 0.7.7.201606060606
Spring Boot
Reporter: Jodi
##Conditions which led to the issue
Prior to the issue occurring, try and use jacoco-maven-plugin with
maven-surefire-plugin while inside a profile to address as yet unknown issues
when adding maven-docker-plugin to pom.xml
##Maven configuration
After:
1. Opening a project POM which hasn't yet been migrated to docker
2. Moving maven-surefire-plugin and jacoco-maven-plugin to a "test" profile
3. Setting plugin version to 2.19.1 in POM
4. Switching to "test" profile
5. Run mvn:build from Netbeans
6. Running mv:test on any specific class
##Outcome
maven-surefire-plugin fails while Forking: Error: Could not find or load main
class ${argLine}
See attached error.log and pom.xml
##Notes
Test fails with or without following pom.xml section commented out in plugin
configuration
...
1
true
...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1262) Add modulepath support
[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430775#comment-15430775
]
Tibor Digana commented on SUREFIRE-1262:
[~rfscholte]
How can I determine the java version using toolchain or maven-sahred-utils?
I would call {{OutputStreamFlushableCommandline#createArg().setLine}} if JDK 9
presents.
> Add modulepath support
> --
>
> Key: SUREFIRE-1262
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1262
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> With the Jigsaw project Java9 is extended with a modulepath. This means that
> surefire should be executed in a different way.
> When working with a modulepath, the Classpath in the MANIFEST of the
> executable jar will be ignored, you need need to add everything on
> commandline.
> Just like javadoc, the java executable has an {{@}} option, where you
> can add arguments per line. So this is the new preferred way to build the
> module-path.
> IIUC for surefire it is important to add {{-Xpatch target/test-classes}}
> which makes it possible to use the same packages as target/classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430755#comment-15430755
]
Tibor Digana edited comment on SUREFIRE-1273 at 8/22/16 1:35 PM:
-
[~jodi.cur...@gmail.com]
see the error in log:
Error: Could not find or load main class ${argLine}
I think your POM should be fixed. For more information see our project
https://github.com/apache/maven-surefire as a hint.
was (Author: tibor17):
[~jodi.cur...@gmail.com]
see the error in log __Error: Could not find or load main class ${argLine}__
I think your POM should be fixed. For more information see our project
https://github.com/apache/maven-surefire as a hint.
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430755#comment-15430755
]
Tibor Digana edited comment on SUREFIRE-1273 at 8/22/16 1:34 PM:
-
[~jodi.cur...@gmail.com]
see the error in log __Error: Could not find or load main class ${argLine}__
I think your POM should be fixed. For more information see our project
https://github.com/apache/maven-surefire as a hint.
was (Author: tibor17):
[~jodi.cur...@gmail.com]
see the error in log *Error: Could not find or load main class ${argLine}*
I think your POM should be fixed. For more information see our project
https://github.com/apache/maven-surefire as a hint.
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430755#comment-15430755
]
Tibor Digana edited comment on SUREFIRE-1273 at 8/22/16 1:34 PM:
-
[~jodi.cur...@gmail.com]
see the error in log *Error: Could not find or load main class ${argLine}*
I think your POM should be fixed. For more information see our project
https://github.com/apache/maven-surefire as a hint.
was (Author: tibor17):
[~jodi.cur...@gmail.com]
see the error in log {{Error: Could not find or load main class ${argLine}}}
I think your POM should be fixed. For more information see our project
https://github.com/apache/maven-surefire as a hint.
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1273) Adding plugin inside Maven profile breaks mvn:build on project
[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430755#comment-15430755
]
Tibor Digana commented on SUREFIRE-1273:
[~jodi.cur...@gmail.com]
see the error in log {{Error: Could not find or load main class ${argLine}}}
I think your POM should be fixed. For more information see our project
https://github.com/apache/maven-surefire as a hint.
> Adding plugin inside Maven profile breaks mvn:build on project
> --
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
>Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
