[jira] [Commented] (MNG-6598) Maven 3.6.0 and Surefire problem
[
https://issues.apache.org/jira/browse/MNG-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117516#comment-17117516
]
Claus Nielsen commented on MNG-6598:
Yes - I can confirm that the MNG-6900 branch fixes this issue :-)
> Maven 3.6.0 and Surefire problem
>
>
> Key: MNG-6598
> URL: https://issues.apache.org/jira/browse/MNG-6598
> Project: Maven
> Issue Type: Task
> Components: General
>Affects Versions: 3.6.0
> Environment: windows 7, 64bit Oracle jdk 1.8 (see stacktrace)
>Reporter: Lars Borup Jensen
>Priority: Critical
> Fix For: 3.7.0-candidate
>
>
> We've been using 3.5.2 for a longer period of time and just recently upgraded
> to 3.6.0 and then the problems started.
> First we experienced way longer build times when running the absolutely same
> build in 3.6.0 than 3.5.2. Using -B when running locally does seem to improve
> build time but still not quite the same.
> The main issue and one that is really causing us headaches is that Surefire
> 2.22.0 suddently started failing to create forks when running tests - setting
> forkCount does help on this, but then we come back to the above mentioned
> problem: build time, which then becomes painfully slow.
> So our discovery is: same source, same POM (same versions of plugins etc)
> fails to build on 3.6.0 but works on 3.5.2 (and even faster) - do you have
> any pointers for us, what to look for?
> Stacktrace from Maven
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on
> project myproj: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\projects\myproj\proj\target\surefire-reports for
> the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6598) Maven 3.6.0 and Surefire problem
[
https://issues.apache.org/jira/browse/MNG-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116638#comment-17116638
]
Claus Nielsen commented on MNG-6598:
I have checked out the branch MNG-6900 and I ran this command:
mvn
-DdistributionTargetDir="c:/projects/maven/target/apache-maven-3.7.x-SNAPSHOT"
clean package
The build produced this error:
{code}
[INFO] Apache Maven ... SUCCESS [ 38.799 s]
[INFO] Maven Model SUCCESS [ 40.950 s]
[INFO] Maven Artifact . SUCCESS [ 7.900 s]
[INFO] Maven Plugin API ... FAILURE [ 3.797 s]
[INFO] Maven Builder Support .. SKIPPED
[INFO] Maven Model Builder SKIPPED
[INFO] Maven Settings . SKIPPED
[INFO] Maven Settings Builder . SKIPPED
[INFO] Maven Repository Metadata Model SKIPPED
[INFO] Maven Artifact Resolver Provider ... SKIPPED
[INFO] Maven Core . SKIPPED
[INFO] Maven SLF4J Wrapper SKIPPED
[INFO] Maven SLF4J Simple Provider SKIPPED
[INFO] Maven Embedder . SKIPPED
[INFO] Maven Compat ... SKIPPED
[INFO] Apache Maven Distribution .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:32 min
[INFO] Finished at: 2020-05-26T13:09:03+02:00
[INFO]
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check
(rat-check) on project maven-plugin-api: Too many files with unapproved
license: 1 See RAT report in: C:\projects\maven\maven-plugin-api\target\rat.txt
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :maven-plugin-api
{code}
Something i'm missing ?
> Maven 3.6.0 and Surefire problem
>
>
> Key: MNG-6598
> URL: https://issues.apache.org/jira/browse/MNG-6598
> Project: Maven
> Issue Type: Task
> Components: General
>Affects Versions: 3.6.0
> Environment: windows 7, 64bit Oracle jdk 1.8 (see stacktrace)
>Reporter: Lars Borup Jensen
>Priority: Critical
> Fix For: 3.7.0-candidate
>
>
> We've been using 3.5.2 for a longer period of time and just recently upgraded
> to 3.6.0 and then the problems started.
> First we experienced way longer build times when running the absolutely same
> build in 3.6.0 than 3.5.2. Using -B when running locally does seem to improve
> build time but still not quite the same.
> The main issue and one that is really causing us headaches is that Surefire
> 2.22.0 suddently started failing to create forks when running tests - setting
> forkCount does help on this, but then we come back to the above mentioned
> problem: build time, which then becomes painfully slow.
> So our discovery is: same source, same POM (same versions of plugins etc)
> fails to build on 3.6.0 but works on 3.5.2 (and even faster) - do you have
> any pointers for us, what to look for?
> Stacktrace from Maven
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on
> project myproj: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\projects\myproj\proj\target\surefire-reports for
> the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
>
[jira] [Commented] (MNG-6598) Maven 3.6.0 and Surefire problem
[
https://issues.apache.org/jira/browse/MNG-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110827#comment-17110827
]
Claus Nielsen commented on MNG-6598:
I guess I need some instructions on how to build Maven from source and use it
locally to confirm. Is it just as simple as running a mvn clean package on the
branch?
> Maven 3.6.0 and Surefire problem
>
>
> Key: MNG-6598
> URL: https://issues.apache.org/jira/browse/MNG-6598
> Project: Maven
> Issue Type: Task
> Components: General
>Affects Versions: 3.6.0
> Environment: windows 7, 64bit Oracle jdk 1.8 (see stacktrace)
>Reporter: Lars Borup Jensen
>Priority: Critical
> Fix For: 3.7.0-candidate
>
>
> We've been using 3.5.2 for a longer period of time and just recently upgraded
> to 3.6.0 and then the problems started.
> First we experienced way longer build times when running the absolutely same
> build in 3.6.0 than 3.5.2. Using -B when running locally does seem to improve
> build time but still not quite the same.
> The main issue and one that is really causing us headaches is that Surefire
> 2.22.0 suddently started failing to create forks when running tests - setting
> forkCount does help on this, but then we come back to the above mentioned
> problem: build time, which then becomes painfully slow.
> So our discovery is: same source, same POM (same versions of plugins etc)
> fails to build on 3.6.0 but works on 3.5.2 (and even faster) - do you have
> any pointers for us, what to look for?
> Stacktrace from Maven
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on
> project myproj: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\projects\myproj\proj\target\surefire-reports for
> the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6598) Maven 3.6.0 and Surefire problem
[
https://issues.apache.org/jira/browse/MNG-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099028#comment-17099028
]
Claus Nielsen commented on MNG-6598:
Yes - it's a confirmation. I have replaced the Jansi library manually on 3.6.3
with both 1.18 and 1.19 and the problem described in this ticket then
disappear. (I work together with the reporter Lars Borup)
> Maven 3.6.0 and Surefire problem
>
>
> Key: MNG-6598
> URL: https://issues.apache.org/jira/browse/MNG-6598
> Project: Maven
> Issue Type: Task
> Components: General
>Affects Versions: 3.6.0
> Environment: windows 7, 64bit Oracle jdk 1.8 (see stacktrace)
>Reporter: Lars Borup Jensen
>Priority: Critical
> Fix For: 3.x / Backlog
>
>
> We've been using 3.5.2 for a longer period of time and just recently upgraded
> to 3.6.0 and then the problems started.
> First we experienced way longer build times when running the absolutely same
> build in 3.6.0 than 3.5.2. Using -B when running locally does seem to improve
> build time but still not quite the same.
> The main issue and one that is really causing us headaches is that Surefire
> 2.22.0 suddently started failing to create forks when running tests - setting
> forkCount does help on this, but then we come back to the above mentioned
> problem: build time, which then becomes painfully slow.
> So our discovery is: same source, same POM (same versions of plugins etc)
> fails to build on 3.6.0 but works on 3.5.2 (and even faster) - do you have
> any pointers for us, what to look for?
> Stacktrace from Maven
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on
> project myproj: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\projects\myproj\proj\target\surefire-reports for
> the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6598) Maven 3.6.0 and Surefire problem
[
https://issues.apache.org/jira/browse/MNG-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098879#comment-17098879
]
Claus Nielsen commented on MNG-6598:
If you replace Jansi 1.17.1 with Jansi 1.18 or Jansi 1.19 the problem reported
here will be fixed. Any plans on upgrading Jansi for Maven 3.6.x ?
> Maven 3.6.0 and Surefire problem
>
>
> Key: MNG-6598
> URL: https://issues.apache.org/jira/browse/MNG-6598
> Project: Maven
> Issue Type: Task
> Components: General
>Affects Versions: 3.6.0
> Environment: windows 7, 64bit Oracle jdk 1.8 (see stacktrace)
>Reporter: Lars Borup Jensen
>Priority: Critical
> Fix For: 3.x / Backlog
>
>
> We've been using 3.5.2 for a longer period of time and just recently upgraded
> to 3.6.0 and then the problems started.
> First we experienced way longer build times when running the absolutely same
> build in 3.6.0 than 3.5.2. Using -B when running locally does seem to improve
> build time but still not quite the same.
> The main issue and one that is really causing us headaches is that Surefire
> 2.22.0 suddently started failing to create forks when running tests - setting
> forkCount does help on this, but then we come back to the above mentioned
> problem: build time, which then becomes painfully slow.
> So our discovery is: same source, same POM (same versions of plugins etc)
> fails to build on 3.6.0 but works on 3.5.2 (and even faster) - do you have
> any pointers for us, what to look for?
> Stacktrace from Maven
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on
> project myproj: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\projects\myproj\proj\target\surefire-reports for
> the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MRELEASE-967) scmCommentPrefix is not used when tagging
Claus Nielsen created MRELEASE-967: -- Summary: scmCommentPrefix is not used when tagging Key: MRELEASE-967 URL: https://issues.apache.org/jira/browse/MRELEASE-967 Project: Maven Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.5.3 Environment: Linux, Maven 3.3.9, jdk 1.0.8_102, GIT Reporter: Claus Nielsen We use a Jira Hook in out GIT installation to ensure a Jira Ticket in all commits. This is of course also activated when the release plugin comes into play. When using release prepare with the scmCommentPrefix parameter, the commit message is not as expected when it comes to tagging. The initial prepare commit where the release version is committed works fine with the scmCommentPrefix, but in the next phase where the actual tagging is made the value in scmCommentPrefix is ignored. This result in a failing release with a lot of manual cleaning up in poms... :-( I can see that there was a problem with this earlier before using scm api 1.3 and before the maven release version 2.0. But this should be fixed now. Here is an example: mvn release:prepare release:perform '-DscmCommentPrefix=NIS-145 NIS-295 (clausfod)' -Dresume=false '-Darguments=-DskipTests' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] Issue Comment Edited: (MSITE-617) Variable substitution in the site url doesn't work
[
https://jira.codehaus.org/browse/MSITE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282499#comment-282499
]
Claus Nielsen edited comment on MSITE-617 at 11/1/11 4:27 AM:
--
Tried this:
UTF-8
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}
sites
Project Website
${siteDeployUrl}
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO]>>> to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT:
bad substitution
And then changed the host name in the site URL:
UTF-8
scp://mXn/data/Maven/sites/${project.artifactId}/${project.version}
sites
Project Website
${siteDeployUrl}
Then a new site:deploy gave this result (I didn't build the site again - just
ran site:deploy):
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO]>>> to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT:
bad substitution
was (Author: clanie):
Tried this:
UTF-8
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}
sites
Project Website
${siteDeployUrl}
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO]>>> to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT:
bad substitution
And this (different host name in the site URL):
UTF-8
scp://mXn/data/Maven/sites/${project.artifactId}/${project.version}
sites
Project Website
${siteDeployUrl}
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO]>>> to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/s
[jira] Commented: (MSITE-617) Variable substitution in the site url doesn't work
[
https://jira.codehaus.org/browse/MSITE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282499#comment-282499
]
Claus Nielsen commented on MSITE-617:
-
Tried this:
UTF-8
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}
sites
Project Website
${siteDeployUrl}
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO]>>> to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT:
bad substitution
And this (different host name in the site URL):
UTF-8
scp://mXn/data/Maven/sites/${project.artifactId}/${project.version}
sites
Project Website
${siteDeployUrl}
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO]>>> to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT:
bad substitution
> Variable substitution in the site url doesn't work
> --
>
> Key: MSITE-617
> URL: https://jira.codehaus.org/browse/MSITE-617
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 2.3
> Environment: Windows 7 and RHEL6
>Reporter: Claus Nielsen
>
> site:deploy fails because variable substitution in the site url no longer
> works (it did in version 2.2).
> The distributionManagement section in out POM looks something like this:
>
>
> sites
> Project Website
>
> scp://server/sites/${project.artifactId}/${project.version}
>
>
> Copying the site to the above mentioned url fails with this message:
> [INFO] Error uploading site
> Embedded error: Error performing commands for file transfer
> Exit code: 1 - bash:
> /sites/${project.artifactId}/${project.version}/../../id-of-the-artifact/0.2.8-SNAPSHOT:
> bad substitution
> Ie. the substitutiuon variables have not been substituted, instead the
> property values have been appended to the url along with a few dots and
> dashes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-617) Variable substitution in the site url doesn't work
Variable substitution in the site url doesn't work
--
Key: MSITE-617
URL: https://jira.codehaus.org/browse/MSITE-617
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: site:deploy
Affects Versions: 2.3
Environment: Windows 7 and RHEL6
Reporter: Claus Nielsen
site:deploy fails because variable substitution in the site url no longer works
(it did in version 2.2).
The distributionManagement section in out POM looks something like this:
sites
Project Website
scp://server/sites/${project.artifactId}/${project.version}
Copying the site to the above mentioned url fails with this message:
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/sites/${project.artifactId}/${project.version}/../../id-of-the-artifact/0.2.8-SNAPSHOT:
bad substitution
Ie. the substitutiuon variables have not been substituted, instead the property
values have been appended to the url along with a few dots and dashes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
