[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674259#comment-16674259 ] Dan Tran commented on SUREFIRE-1359: [~MattNelson] I am experiencing the same issue. maven 3.6 java 1.8.0-171. How did you implement the workaround? > Corrupted stdin stream in forked JVM 1. See the dump file > - > > Key: SUREFIRE-1359 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1359 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.20 > Environment: JDK 1.8.0_121 > maven version 3.5.0 >Reporter: Brian Oxley >Assignee: Tibor Digana >Priority: Major > Attachments: 2017-04-13T10-56-35_635-jvmRun1.dumpstream, > 2017-04-13T10-56-36_592.dumpstream, TEST-hm.binkley.labs.GitInfoIT.xml, > TEST-hm.binkley.labs.GreetingControllerIT.xml, failsafe-summary.xml, > hm.binkley.labs.GitInfoIT.txt, hm.binkley.labs.GreetingControllerIT.txt > > > Surefire 2.20 complains "Corrupted stdin stream in forked JVM 1. See the dump > file". Version 2.19.1 does not, and testing completes successfully. > Project is here: https://github.com/binkley/sproingk. > Run with "mvn clean verify". > Same behavior on Windows 10 (Oracle JDK), MacOS and the Linux subsystem on > Windows. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCOMPILER-205) maven-compiler-plugin: incremental compilation broken
[
https://issues.apache.org/jira/browse/MCOMPILER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674161#comment-16674161
]
Jens Bannmann commented on MCOMPILER-205:
-
[~rfscholte], could you please clarify and expand on the following comment?
{quote}The reason is that the default java compiler is quite fast, likely much
faster than analyzing per file what to do with it.
{quote}
It seems that despite that comment and my attempt at explaining everything in
the SO answer [~Didier Loiseau] kindly linked, there is still confusion, as
some added the following comment ("the developer" and "he" referring to
[~rfscholte]):
{quote}I think you have misread the developers comment. I was scratching my
head at first but I think what he meant was that the default incremental
compilation provided by javac is fast. I very much doubt he meant that
recompiling everything each time you make a change is preferable. You only need
a project of >100 source-files to show that's nonsense.
{quote}
> maven-compiler-plugin: incremental compilation broken
> -
>
> Key: MCOMPILER-205
> URL: https://issues.apache.org/jira/browse/MCOMPILER-205
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Lukas Fryc
>Priority: Major
> Attachments: hello.tgz, ignore-package-info.patch,
> no-class-in-java-file.zip, only-recompile-changed.patch
>
>
> When we do {{clean}} -> {{compile}} -> {{compile}}, all Java sources are
> re-compiled for second compilation steps:
> {code}
> [framework]$ mvn clean
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> {code}
> The source code of the affected project:
> https://github.com/richfaces/richfaces5/tree/077dcfc0a46d03d7ba9a7ac3e701a4adfb834c71
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1198) Failsafe does not allow to configure the jar file to use
[
https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674157#comment-16674157
]
Rustam Abdullaev commented on SUREFIRE-1198:
Ah OK thanks! We don't inherit from spring-boot-starter-parent (because we must
inherit from our corporate parent pom), so didn't have that configuration. It's
working now indeed.
> Failsafe does not allow to configure the jar file to use
>
>
> Key: SUREFIRE-1198
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1198
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.20
>
>
> See [this Spring Boot
> issue|https://github.com/spring-projects/spring-boot/issues/4510#issuecomment-159448634]
> It seems that SUREFIRE-855 does not allow {{target/classes}} to be used
> anymore. Is there a reason why this behaviour was completely removed in
> favour of only the jar file?
> It would be nice if we had an option to chose between the two (defaulting to
> the jar)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MRELEASE-1017) The option -Dproject.scm.developerConnection as specified in the guide does not work
[ https://issues.apache.org/jira/browse/MRELEASE-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Belden updated MRELEASE-1017: Description: What I'm reporting is basically the same as the following which looks to never have been resolved. https://issues.apache.org/jira/browse/MRELEASE-707 The option -Dproject.scm.developerConnection as specified on the following guide does not work. [https://maven.apache.org/guides/mini/guide-releasing.html] It would be nice if the documentation could be updated so as not to be misleading. However it would be even nicer to have that functionality, as it is a critical configuration in order to be able to use this plugin in modern CI/CD pipelines. Is such a configuration planned for any future release? I have already bolted this functionality onto the 2.5.3 source so that I can at least use this on my projects. Otherwise this plugin is not usable for my team, hence why I am marking this as major. But I do not understand the procedure for sharing this feature, or if it's already being added to a future release then it's a moot point. was: What I'm reporting is basically the same as the following which looks to never have been resolved. https://issues.apache.org/jira/browse/MRELEASE-707 The option -Dproject.scm.developerConnection as specified on the following guide does not work. [https://maven.apache.org/guides/mini/guide-releasing.html] It would be nice if the documentation could be updated so as not to be misleading. However it would be even nicer to have that functionality, as it is a critical configuration in order to be able to use this plugin in modern CI/CD pipelines. Is such a configuration planned for any future release? I have already bolted this functionality onto the 2.5.3 source so that I can at least use this on my projects. Otherwise this plugin is not usable for my team. But I do not understand the procedure for sharing this feature, or if it's already being added to a future release then it's a moot point. > The option -Dproject.scm.developerConnection as specified in the guide does > not work > > > Key: MRELEASE-1017 > URL: https://issues.apache.org/jira/browse/MRELEASE-1017 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5.3 >Reporter: George Belden >Priority: Major > > What I'm reporting is basically the same as the following which looks to > never have been resolved. > https://issues.apache.org/jira/browse/MRELEASE-707 > > The option -Dproject.scm.developerConnection as specified on the following > guide does not work. > [https://maven.apache.org/guides/mini/guide-releasing.html] > > It would be nice if the documentation could be updated so as not to be > misleading. However it would be even nicer to have that functionality, as it > is a critical configuration in order to be able to use this plugin in modern > CI/CD pipelines. > Is such a configuration planned for any future release? I have already > bolted this functionality onto the 2.5.3 source so that I can at least use > this on my projects. Otherwise this plugin is not usable for my team, hence > why I am marking this as major. But I do not understand the procedure for > sharing this feature, or if it's already being added to a future release then > it's a moot point. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MRELEASE-1017) The option -Dproject.scm.developerConnection as specified in the guide does not work
[ https://issues.apache.org/jira/browse/MRELEASE-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Belden updated MRELEASE-1017: Priority: Major (was: Blocker) > The option -Dproject.scm.developerConnection as specified in the guide does > not work > > > Key: MRELEASE-1017 > URL: https://issues.apache.org/jira/browse/MRELEASE-1017 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5.3 >Reporter: George Belden >Priority: Major > > What I'm reporting is basically the same as the following which looks to > never have been resolved. > https://issues.apache.org/jira/browse/MRELEASE-707 > > The option -Dproject.scm.developerConnection as specified on the following > guide does not work. > [https://maven.apache.org/guides/mini/guide-releasing.html] > > It would be nice if the documentation could be updated so as not to be > misleading. However it would be even nicer to have that functionality, as it > is a critical configuration in order to be able to use this plugin in modern > CI/CD pipelines. > Is such a configuration planned for any future release? I have already > bolted this functionality onto the 2.5.3 source so that I can at least use > this on my projects. Otherwise this plugin is not usable for my team. But I > do not understand the procedure for sharing this feature, or if it's already > being added to a future release then it's a moot point. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MRELEASE-1017) The option -Dproject.scm.developerConnection as specified in the guide does not work
[ https://issues.apache.org/jira/browse/MRELEASE-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Belden updated MRELEASE-1017: Priority: Blocker (was: Minor) > The option -Dproject.scm.developerConnection as specified in the guide does > not work > > > Key: MRELEASE-1017 > URL: https://issues.apache.org/jira/browse/MRELEASE-1017 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5.3 >Reporter: George Belden >Priority: Blocker > > What I'm reporting is basically the same as the following which looks to > never have been resolved. > https://issues.apache.org/jira/browse/MRELEASE-707 > > The option -Dproject.scm.developerConnection as specified on the following > guide does not work. > [https://maven.apache.org/guides/mini/guide-releasing.html] > > It would be nice if the documentation could be updated so as not to be > misleading. However it would be even nicer to have that functionality, as it > is a critical configuration in order to be able to use this plugin in modern > CI/CD pipelines. > Is such a configuration planned for any future release? I have already > bolted this functionality onto the 2.5.3 source so that I can at least use > this on my projects. Otherwise this plugin is not usable for my team. But I > do not understand the procedure for sharing this feature, or if it's already > being added to a future release then it's a moot point. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MRELEASE-1017) The option -Dproject.scm.developerConnection as specified in the guide does not work
George Belden created MRELEASE-1017: --- Summary: The option -Dproject.scm.developerConnection as specified in the guide does not work Key: MRELEASE-1017 URL: https://issues.apache.org/jira/browse/MRELEASE-1017 Project: Maven Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.5.3 Reporter: George Belden What I'm reporting is basically the same as the following which looks to never have been resolved. https://issues.apache.org/jira/browse/MRELEASE-707 The option -Dproject.scm.developerConnection as specified on the following guide does not work. [https://maven.apache.org/guides/mini/guide-releasing.html] It would be nice if the documentation could be updated so as not to be misleading. However it would be even nicer to have that functionality, as it is a critical configuration in order to be able to use this plugin in modern CI/CD pipelines. Is such a configuration planned for any future release? I have already bolted this functionality onto the 2.5.3 source so that I can at least use this on my projects. Otherwise this plugin is not usable for my team. But I do not understand the procedure for sharing this feature, or if it's already being added to a future release then it's a moot point. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SUREFIRE-1198) Failsafe does not allow to configure the jar file to use
[
https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674086#comment-16674086
]
Stephane Nicoll edited comment on SUREFIRE-1198 at 11/3/18 3:47 PM:
I don't thinks that error is related to this issue. Spring Boot is using
Failsafe 2.22.1 in {{spring-boot-starter-parent}} with this extra configuration
{noformat}
${project.build.outputDirectory}
{noformat}
was (Author: snicoll):
I don't thinks that error is related to this issue. Spring Boot is using
Failsafe 2.22.1 in {{spring-boot-starter-parent}} with this extra configuration
{{noformat}}
${project.build.outputDirectory}
{{noformat}}
> Failsafe does not allow to configure the jar file to use
>
>
> Key: SUREFIRE-1198
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1198
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.20
>
>
> See [this Spring Boot
> issue|https://github.com/spring-projects/spring-boot/issues/4510#issuecomment-159448634]
> It seems that SUREFIRE-855 does not allow {{target/classes}} to be used
> anymore. Is there a reason why this behaviour was completely removed in
> favour of only the jar file?
> It would be nice if we had an option to chose between the two (defaulting to
> the jar)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1198) Failsafe does not allow to configure the jar file to use
[
https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674086#comment-16674086
]
Stephane Nicoll commented on SUREFIRE-1198:
---
I don't thinks that error is related to this issue. Spring Boot is using
Failsafe 2.22.1 in {{spring-boot-starter-parent}} with this extra configuration
{{noformat}}
${project.build.outputDirectory}
{{noformat}}
> Failsafe does not allow to configure the jar file to use
>
>
> Key: SUREFIRE-1198
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1198
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.20
>
>
> See [this Spring Boot
> issue|https://github.com/spring-projects/spring-boot/issues/4510#issuecomment-159448634]
> It seems that SUREFIRE-855 does not allow {{target/classes}} to be used
> anymore. Is there a reason why this behaviour was completely removed in
> favour of only the jar file?
> It would be nice if we had an option to chose between the two (defaulting to
> the jar)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[
https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674063#comment-16674063
]
Anton commented on SUREFIRE-1541:
-
maven:3.6.0-jdk-8 surefire 2.22.1 - FAILED
https://gitlab.com/anton_patsev/java-junit-sample/-/jobs/116087079
> SurefireBooterForkException: The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> --
>
> Key: SUREFIRE-1541
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1541
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.22.0
>Reporter: Anghel Botos
>Priority: Major
>
> Attempting to run integration tests using maven-failsafe-plugin with
> {{-Dmaven.failsafe.debug=false}} yields the following stacktrace:
>
> {noformat}
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was cmd.exe /X /C ""C:\Program
> Files\Java\jdk1.8.0_121\jre\bin\java" false -jar
> C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar
> C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485
> 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp
> surefire_411836142070426630764tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> {noformat}
>
> The issue is the "free-floating" {{false}} that appears in the command line
> used to start a new JVM. I've traced down the issue to
> {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}}
> where the following code can be found:
> {code:java}
> String debugForkedProcess = getDebugForkedProcess();
> if ( "true".equals( debugForkedProcess ) )
> {
> return "-Xdebug -Xnoagent -Djava.compiler=NONE"
> + "
> -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005";
> }
> return debugForkedProcess;
> {code}
> ...which is quite..."unexpected" to see that one can pass in a value of
> {{true}}, but not a value of {{false}}.
> Please fix with a proper parsing of true/false values for the
> {{maven.failsafe.debug}} property.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (SUREFIRE-1198) Failsafe does not allow to configure the jar file to use
[
https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674062#comment-16674062
]
Rustam Abdullaev edited comment on SUREFIRE-1198 at 11/3/18 2:32 PM:
-
Failsafe is NOT working with Spring Boot in repackage mode since version 2.19.
{code:java}
org.springframework.boot
spring-boot-maven-plugin
2.1.0.RELEASE
repackage
{code}
Causes
{code:java}
java.lang.ArrayStoreException:
sun.reflect.annotation.TypeNotPresentExceptionProxy
at
sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724)
at
sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531)
at
sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355)
at
sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72)
at java.lang.Class.createAnnotationData(Class.java:3521)
at java.lang.Class.annotationData(Class.java:3510)
at java.lang.Class.getAnnotation(Class.java:3415)
at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.isValidJUnit4Test(JUnit4TestChecker.java:66)
at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.accept(JUnit4TestChecker.java:53)
at
org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:102)
at
org.apache.maven.surefire.junit4.JUnit4Provider.scanClassPath(JUnit4Provider.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.setTestsToRun(JUnit4Provider.java:189)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:132)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
{code}
So we're stuck with version *2.18.1* at the moment.
How to use Failsafe with the repackage goal?
was (Author: rustamabd):
Failsafe is NOT working with Spring Boot in repackage mode since version 2.19.
{code}
org.springframework.boot
spring-boot-maven-plugin
2.1.0.RELEASE
repackage
{code}
Causes
{code}
java.lang.ArrayStoreException:
sun.reflect.annotation.TypeNotPresentExceptionProxy
at
sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724)
at
sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531)
at
sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355)
at
sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72)
at java.lang.Class.createAnnotationData(Class.java:3521)
at java.lang.Class.annotationData(Class.java:3510)
at java.lang.Class.getAnnotation(Class.java:3415)
at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.isValidJUnit4Test(JUnit4TestChecker.java:66)
at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.accept(JUnit4TestChecker.java:53)
at
org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:102)
at
org.apache.maven.surefire.junit4.JUnit4Provider.scanClassPath(JUnit4Provider.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.setTestsToRun(JUnit4Provider.java:189)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:132)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
{code}
So we're stuck with version *2.18.1* at the moment.
How to
[jira] [Commented] (SUREFIRE-1198) Failsafe does not allow to configure the jar file to use
[
https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674062#comment-16674062
]
Rustam Abdullaev commented on SUREFIRE-1198:
Failsafe is NOT working with Spring Boot in repackage mode since version 2.19.
{code}
org.springframework.boot
spring-boot-maven-plugin
2.1.0.RELEASE
repackage
{code}
Causes
{code}
java.lang.ArrayStoreException:
sun.reflect.annotation.TypeNotPresentExceptionProxy
at
sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724)
at
sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531)
at
sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355)
at
sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72)
at java.lang.Class.createAnnotationData(Class.java:3521)
at java.lang.Class.annotationData(Class.java:3510)
at java.lang.Class.getAnnotation(Class.java:3415)
at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.isValidJUnit4Test(JUnit4TestChecker.java:66)
at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.accept(JUnit4TestChecker.java:53)
at
org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:102)
at
org.apache.maven.surefire.junit4.JUnit4Provider.scanClassPath(JUnit4Provider.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.setTestsToRun(JUnit4Provider.java:189)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:132)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
{code}
So we're stuck with version *2.18.1* at the moment.
How to use Surefire with the repackage goal?
> Failsafe does not allow to configure the jar file to use
>
>
> Key: SUREFIRE-1198
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1198
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.20
>
>
> See [this Spring Boot
> issue|https://github.com/spring-projects/spring-boot/issues/4510#issuecomment-159448634]
> It seems that SUREFIRE-855 does not allow {{target/classes}} to be used
> anymore. Is there a reason why this behaviour was completely removed in
> favour of only the jar file?
> It would be nice if we had an option to chose between the two (defaulting to
> the jar)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MRELEASE-797) support semantic versioning
[
https://issues.apache.org/jira/browse/MRELEASE-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674046#comment-16674046
]
Thomas Meyer commented on MRELEASE-797:
---
mhh. okay. My use case is to create release versions with the maven
release-plugin. I either want to automatically increment the minor or patch
version. I want to set an java property and let do the maven-release-plugin the
magic. It feels wrong to bind the version policy to a given maven project. the
release number policy should only be an command line option and not bound to a
given project at least that's my view on this topic.
but for the current SemVerPolicy to work and having tens of different maven
project, for each project you must configure a dependency to this artifact and
change their pom. yes you could do an parent pom, but its very complicated
given that you just want to create a releae version of a given artifact.
I bet this is the reason that most users of the maven-release-plugin just
manually provide the release and snapshot version via command line options.
searching the net for the already available OddEvenPolicy reveals nearly no
hits, besides the plugin itself, and some source code.
> support semantic versioning
> ---
>
> Key: MRELEASE-797
> URL: https://issues.apache.org/jira/browse/MRELEASE-797
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: update-versions
>Affects Versions: 2.3.2
> Environment: Maven 3.0.4
>Reporter: Matthew Daniel
>Assignee: Robert Scholte
>Priority: Minor
>
> When a project is using [semantic versioning|http://semver.org/], the
> maven-release-plugin will only increment the right-most version identifier
> (which corresponds to a "patch" release in semver terminology). It would be
> helpful if the maven-release-plugin understood the 3 normal release
> severities: major, minor and patch.
> Current behavior:
> # Given a {{pom.xml}} with version {{1.0.50-SNAPSHOT}}
> # When the user executes {{mvn release:update-versions -Dsemver=major}} (as a
> hypothetical syntax)
> # Then observe that {{pom.xml}} contains {{1.0.51-SNAPSHOT}}, not
> {{2.0.0-SNAPSHOT}} as a "major" release would dictate
> Expected behavior:
> # Given a pom version in {{X.Y.Z}} format
> # When one indicates the desired semantic version release level to
> maven-release-plugin
> # Then maven-release-plugin increments {{X.Y.Z}} according to the user's
> indicated release level
> It would be an error condition for the user to request a semantic version
> release level when the pom's version is not in {{X.Y.Z}} format (plus any
> miscellaneous trailing text as specified in rules 10, 11 or 12 of the semver
> specification).
> It is currently possible to work around this via manual construction of a
> {{release.properties}} file, but that requires a 2 step build process: run
> the script then run the Maven targets. Further, one would expect that all
> Maven projects that use semantic versioning would need to implement their own
> pre-release scripts, which is wasteful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARCHETYPE-557) Upgrade surefire to 2.22.1
[ https://issues.apache.org/jira/browse/ARCHETYPE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674039#comment-16674039 ] Karl Heinz Marbaise commented on ARCHETYPE-557: --- Done in [0cf766862a8fb04bf5df5f2ff4981eaff8cf076b|https://gitbox.apache.org/repos/asf?p=maven-archetype.git;a=commitdiff;h=0cf766862a8fb04bf5df5f2ff4981eaff8cf076b] > Upgrade surefire to 2.22.1 > -- > > Key: ARCHETYPE-557 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-557 > Project: Maven Archetype > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.2 > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARCHETYPE-557) Upgrade surefire to 2.22.1
[ https://issues.apache.org/jira/browse/ARCHETYPE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed ARCHETYPE-557. - Resolution: Done > Upgrade surefire to 2.22.1 > -- > > Key: ARCHETYPE-557 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-557 > Project: Maven Archetype > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.2 > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MSCMPUB-39) Upgrade maven-plugins parent to 33.
[ https://issues.apache.org/jira/browse/MSCMPUB-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MSCMPUB-39: -- Assignee: Karl Heinz Marbaise > Upgrade maven-plugins parent to 33. > --- > > Key: MSCMPUB-39 > URL: https://issues.apache.org/jira/browse/MSCMPUB-39 > Project: Maven SCM Publish Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSCMPUB-39) Upgrade maven-plugins parent to 33.
Karl Heinz Marbaise created MSCMPUB-39: -- Summary: Upgrade maven-plugins parent to 33. Key: MSCMPUB-39 URL: https://issues.apache.org/jira/browse/MSCMPUB-39 Project: Maven SCM Publish Plugin Issue Type: Dependency upgrade Affects Versions: 3.1.0 Reporter: Karl Heinz Marbaise Fix For: 3.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674037#comment-16674037
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-435585356
Feedback for everybody. We are on the Slack ASF chat with @cstamas and we
are fixing and testing old ITs one by one and the changes are being pushed to
the branch "buildfix" on Surefire project, and @cstamas has his own branch, so
we cooperate. Pls be patient while we are working on current issues. Thx
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7) URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-435585356 Feedback for everybody. We are on the Slack ASF chat with @cstamas and we are fixing and testing old ITs one by one and the changes are being pushed to the branch "buildfix" on Surefire project, and @cstamas has his own branch, so we cooperate. Pls be patient while we are working on current issues. Thx This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (ARCHETYPE-551) Upgrade maven-invoker to 3.0.1
[ https://issues.apache.org/jira/browse/ARCHETYPE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated ARCHETYPE-551: -- Description: Currently not possible otherwise we need to lift the JDK minimum to JDK 7... > Upgrade maven-invoker to 3.0.1 > -- > > Key: ARCHETYPE-551 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-551 > Project: Maven Archetype > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.2 > > > Currently not possible otherwise we need to lift the JDK minimum to JDK 7... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARCHETYPE-557) Upgrade surefire to 2.22.1
Karl Heinz Marbaise created ARCHETYPE-557: - Summary: Upgrade surefire to 2.22.1 Key: ARCHETYPE-557 URL: https://issues.apache.org/jira/browse/ARCHETYPE-557 Project: Maven Archetype Issue Type: Dependency upgrade Affects Versions: 3.0.2 Reporter: Karl Heinz Marbaise Fix For: 3.0.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ARCHETYPE-557) Upgrade surefire to 2.22.1
[ https://issues.apache.org/jira/browse/ARCHETYPE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned ARCHETYPE-557: - Assignee: Karl Heinz Marbaise > Upgrade surefire to 2.22.1 > -- > > Key: ARCHETYPE-557 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-557 > Project: Maven Archetype > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.2 > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPH-154) The output of the plugin should be flushed when using forceStdout
[
https://issues.apache.org/jira/browse/MPH-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MPH-154:
---
Summary: The output of the plugin should be flushed when using forceStdout
(was: The output of the plugin should contain a line-ending)
> The output of the plugin should be flushed when using forceStdout
> -
>
> Key: MPH-154
> URL: https://issues.apache.org/jira/browse/MPH-154
> Project: Maven Help Plugin
> Issue Type: Improvement
>Reporter: Patrick van Rhijn
>Priority: Major
>
> When you use the plugin the output doesn't contain a line-ending making the
> output hard to use in scripting when you have JAVA_OPTIONS defined.
> In the current situation the plugin gives me the following output:
> $ mvn -N -q org.apache.maven.plugins:maven-help-plugin:3.1.0:evaluate
> -Dexpression='project.groupId' -DforceStdout=true
> *nl.foo.barPicked up _JAVA_OPTIONS: -XX:+ForceTimeHighResolution
> -Dsun.java2d.noddraw=true -Duser.timezone='Europe/Amsterdam'*
> It would be better if the output would be divided over two lines and look
> like the output of the exec-maven-plugin:
> $ mvn -N -q -Dexec.executable='echo' -Dexec.args='${project.groupId}'
> org.codehaus.mojo:exec-maven-plugin:1.4.0:exec
> *nl.foo.bar*
> *Picked up _JAVA_OPTIONS: -XX:+ForceTimeHighResolution
> -Dsun.java2d.noddraw=true -Duser.timezone='Europe/Amsterdam'*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJMOD-19) Upgrade plexus-java 0.9.11
[ https://issues.apache.org/jira/browse/MJMOD-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674014#comment-16674014 ] Hudson commented on MJMOD-19: - Build succeeded in Jenkins: Maven TLP » maven-jmod-plugin » master #27 See https://builds.apache.org/job/maven-box/job/maven-jmod-plugin/job/master/27/ > Upgrade plexus-java 0.9.11 > -- > > Key: MJMOD-19 > URL: https://issues.apache.org/jira/browse/MJMOD-19 > Project: Maven JMod Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJLINK-31) Upgrade plexus-java 0.9.11
[ https://issues.apache.org/jira/browse/MJLINK-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674013#comment-16674013 ] Hudson commented on MJLINK-31: -- Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » master #37 See https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/master/37/ > Upgrade plexus-java 0.9.11 > -- > > Key: MJLINK-31 > URL: https://issues.apache.org/jira/browse/MJLINK-31 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJMOD-19) Upgrade plexus-java 0.9.11
[ https://issues.apache.org/jira/browse/MJMOD-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674011#comment-16674011 ] Karl Heinz Marbaise commented on MJMOD-19: -- Done in [26b45bc7369c24cc49a02ad3a50425aa646edde8|https://gitbox.apache.org/repos/asf?p=maven-jmod-plugin.git;a=commitdiff;h=26b45bc7369c24cc49a02ad3a50425aa646edde8] > Upgrade plexus-java 0.9.11 > -- > > Key: MJMOD-19 > URL: https://issues.apache.org/jira/browse/MJMOD-19 > Project: Maven JMod Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MJMOD-19) Upgrade plexus-java 0.9.11
[ https://issues.apache.org/jira/browse/MJMOD-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJMOD-19. Resolution: Done > Upgrade plexus-java 0.9.11 > -- > > Key: MJMOD-19 > URL: https://issues.apache.org/jira/browse/MJMOD-19 > Project: Maven JMod Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MJLINK-31) Upgrade plexus-java 0.9.11
[ https://issues.apache.org/jira/browse/MJLINK-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJLINK-31. - Resolution: Done > Upgrade plexus-java 0.9.11 > -- > > Key: MJLINK-31 > URL: https://issues.apache.org/jira/browse/MJLINK-31 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJLINK-31) Upgrade plexus-java 0.9.11
[ https://issues.apache.org/jira/browse/MJLINK-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674010#comment-16674010 ] Karl Heinz Marbaise commented on MJLINK-31: --- Done in [21f87a1d490cfef9c8becc9fdd41bb65d2f6bf33|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=21f87a1d490cfef9c8becc9fdd41bb65d2f6bf33] > Upgrade plexus-java 0.9.11 > -- > > Key: MJLINK-31 > URL: https://issues.apache.org/jira/browse/MJLINK-31 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MJLINK-31) Upgrade plexus-java 0.9.11
Karl Heinz Marbaise created MJLINK-31: - Summary: Upgrade plexus-java 0.9.11 Key: MJLINK-31 URL: https://issues.apache.org/jira/browse/MJLINK-31 Project: Maven JLink Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MJLINK-31) Upgrade plexus-java 0.9.11
[ https://issues.apache.org/jira/browse/MJLINK-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MJLINK-31: - Assignee: Karl Heinz Marbaise > Upgrade plexus-java 0.9.11 > -- > > Key: MJLINK-31 > URL: https://issues.apache.org/jira/browse/MJLINK-31 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MJMOD-19) Upgrade plexus-java 0.9.11
Karl Heinz Marbaise created MJMOD-19: Summary: Upgrade plexus-java 0.9.11 Key: MJMOD-19 URL: https://issues.apache.org/jira/browse/MJMOD-19 Project: Maven JMod Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0-alpha-2 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0-alpha-2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6444) Internal code should prefer Path over File
[
https://issues.apache.org/jira/browse/MNG-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6444:
---
Description: Goal is to replace all '{{new File(}}' appearances with Path /
Paths https://docs.oracle.com/javase/7/docs/api/java/nio/file/Path.html (was:
Goal is to replace all '{{new File(}}' appearances with Path / Paths)
> Internal code should prefer Path over File
> --
>
> Key: MNG-6444
> URL: https://issues.apache.org/jira/browse/MNG-6444
> Project: Maven
> Issue Type: Task
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Minor
> Labels: requires-java8
>
> Goal is to replace all '{{new File(}}' appearances with Path / Paths
> https://docs.oracle.com/javase/7/docs/api/java/nio/file/Path.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6239) jansi messes up System.err and System.out
[
https://issues.apache.org/jira/browse/MNG-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673981#comment-16673981
]
Simone Bordet commented on MNG-6239:
[~gboue] adding a {{flush()}} call after the prints does not help: somehow the
output is buffered anyway and only after many prints the output is actually
printed, although not completely (some is still buffered).
[~khmarbaise] the problem still exist in Maven 3.6.0 and again the only
solution is to remove {{jansi}} from {{$MAVEN/lib/}}.
> jansi messes up System.err and System.out
> -
>
> Key: MNG-6239
> URL: https://issues.apache.org/jira/browse/MNG-6239
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.5.0
> Environment: Java 1.8.0_131, Ubuntu 17.04
>Reporter: Simone Bordet
>Priority: Minor
> Attachments: mvn-jansi.tgz
>
>
> I use the Maven Exec Plugin to run a class that asks for interactive input
> from the user. This was working in 3.3.9, but does not work in 3.5.0.
> Anything printed on {{System.err}} or {{System.out}} without a newline is not
> printed immediately on the terminal window.
> Example:
> {code:java}
> BufferedReader console = new BufferedReader(new InputStreamReader(System.in));
> System.err.printf("listen port: ");
> String value = console.readLine().trim();
> {code}
> The example above would not print {{listen port:}} on the terminal.
> Attached you can find a project that reproduces this issue.
> Unpack the project and then run:
> {noformat}
> $ mvn install && mvn exec:exec
> {noformat}
> The expected output of the reproducer would be:
> {noformat}
> err.println
> out.println
> err.printerr.printfout.printout.printf
> {noformat}
> instead I get:
> {noformat}
> err.println
> out.println
> {noformat}
> Removing {{jansi-1.13.jar}} from {{$MAVEN/lib/}} fixes the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MRELEASE-797) support semantic versioning
[
https://issues.apache.org/jira/browse/MRELEASE-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673979#comment-16673979
]
Robert Scholte commented on MRELEASE-797:
-
It has been quite some time since I had a look at that code.
Pure SemVer is now not possible, because the major version should be based on
compatibility. You can only do that after compilation, however Maven expects a
version from the start. I don't know about the status of the current module,
would be nice to see improvements on it when possible.
You should only have to specify the policy in the root-folder, from where the
maven-release-plugin is executed.
> support semantic versioning
> ---
>
> Key: MRELEASE-797
> URL: https://issues.apache.org/jira/browse/MRELEASE-797
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: update-versions
>Affects Versions: 2.3.2
> Environment: Maven 3.0.4
>Reporter: Matthew Daniel
>Assignee: Robert Scholte
>Priority: Minor
>
> When a project is using [semantic versioning|http://semver.org/], the
> maven-release-plugin will only increment the right-most version identifier
> (which corresponds to a "patch" release in semver terminology). It would be
> helpful if the maven-release-plugin understood the 3 normal release
> severities: major, minor and patch.
> Current behavior:
> # Given a {{pom.xml}} with version {{1.0.50-SNAPSHOT}}
> # When the user executes {{mvn release:update-versions -Dsemver=major}} (as a
> hypothetical syntax)
> # Then observe that {{pom.xml}} contains {{1.0.51-SNAPSHOT}}, not
> {{2.0.0-SNAPSHOT}} as a "major" release would dictate
> Expected behavior:
> # Given a pom version in {{X.Y.Z}} format
> # When one indicates the desired semantic version release level to
> maven-release-plugin
> # Then maven-release-plugin increments {{X.Y.Z}} according to the user's
> indicated release level
> It would be an error condition for the user to request a semantic version
> release level when the pom's version is not in {{X.Y.Z}} format (plus any
> miscellaneous trailing text as specified in rules 10, 11 or 12 of the semver
> specification).
> It is currently possible to work around this via manual construction of a
> {{release.properties}} file, but that requires a 2 step build process: run
> the script then run the Maven targets. Further, one would expect that all
> Maven projects that use semantic versioning would need to implement their own
> pre-release scripts, which is wasteful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673974#comment-16673974
]
Tibor Digana commented on SUREFIRE-1588:
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=23427bbcb3dfb7d678ad0f807ea6bdff228cc421
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6374) ModelBuilder hangs with malformed pom.xml
[
https://issues.apache.org/jira/browse/MNG-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-6374:
-
Priority: Minor (was: Major)
> ModelBuilder hangs with malformed pom.xml
> -
>
> Key: MNG-6374
> URL: https://issues.apache.org/jira/browse/MNG-6374
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.5.2, 3.5.3
>Reporter: Rohan Padhye
>Priority: Minor
>
> Maven hangs when provided with a malformed pom.xml file that contains a
> question mark in a tag name.
> Minimal example for a pom.xml:
> {noformat}
> {noformat}
>
> Running {{mvn}} results in the output:
> {noformat}
> [INFO] Scanning for projects...{noformat}
>
> And is stuck there forever, instead of providing an error message.
> I found this issue using [JQF|https://github.com/rohanpadhye/jqf].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MGPG-68) maven-gpg-plugin doesn't actually work with gpgv2
[
https://issues.apache.org/jira/browse/MGPG-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MGPG-68.
---
Resolution: Not A Problem
I can and I will do based on your comment. Thanks for the feedback.
> maven-gpg-plugin doesn't actually work with gpgv2
> -
>
> Key: MGPG-68
> URL: https://issues.apache.org/jira/browse/MGPG-68
> Project: Maven GPG Plugin
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Allen Wittenauer
>Priority: Major
>
> The documentation states:
> {code}
> Passes --use-agent or --no-use-agent to gpg. If using an agent, the
> passphrase is optional as the agent will provide it. For gpg2, specify true
> as --no-use-agent was removed in gpg2 and doesn't ask for a passphrase
> anymore.
> Default value is: true.
> User property is: gpg.useagent.
> {code}
> ... except setting gpg.useagent to true results in '--use-agent' being passed
> which also isn't supported (at least by gpg v2.1.11). There really needs to
> be a 3rd option here.
> Sidenote: the top level Apache pom is trying to set '--digest-algo=SHA512'
> which also isn't supported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673964#comment-16673964
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-435569639
@cstamas
I have fixed that problem. My bad, the reportsDir should be passed via
method and not constructor to the ForkedCnfig because the dir is parameterized
and it can be resolved only via the method.
Can I fix it in master now and finish the release?
The ITs failed because they expected only one dump file and tried to search
a text in all of them but of course the second dump does not have expected text
to assert.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7) URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-435569639 @cstamas I have fixed that problem. My bad, the reportsDir should be passed via method and not constructor to the ForkedCnfig because the dir is parameterized and it can be resolved only via the method. Can I fix it in master now and finish the release? The ITs failed because they expected only one dump file and tried to search a text in all of them but of course the second dump does not have expected text to assert. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
