[jira] [Commented] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169250#comment-16169250
]
Hervé Boutemy commented on MNG-6242:
thanks for your positive report
On adding the option to mvn script, I fear this is not an option: this would
affect any Unix user (Linux, Mac, FreeBSD, ...) and not only Windows+Cygwin
users
Notice that, after releasing Maven 3.5.1 where we have MNG-6282 that is a wider
regression, if we release Maven 3.5.2 without Jansi fix, I'll add in Maven the
workaround code I proposed in
https://github.com/fusesource/jansi/issues/94#issuecomment-329977920
Then whatever happens, Maven will have an improved Jansi detection, be it done
at any level
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Priority: Minor
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-6282) Console output has no colors in shell (both Git Bash and Cygwin) [regression in Jansi 1.16 / Maven 3.5.1]
[ https://issues.apache.org/jira/browse/MNG-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169252#comment-16169252 ] Hervé Boutemy commented on MNG-6282: just for the records, as detailed on https://github.com/fusesource/jansi/issues/94#issuecomment-329976333 , the root cause looks like Cygwin and MSYS don't create real terminals but pseudo-terminals, that isatty -- as expected -- detects as non-terminal, then Jansi has to implement additional pseudo terminal detection from Cygwin and MSYS naming convention, as it is done in Git for Windows https://github.com/git/git/commit/86924838e3d881cda2192fd79ac3a58aad75efd3 thank you [~dejan2609] for your help on this one, without you, I would not have found the root cause. It's great to have multiple people, with multiple approaches, working together > Console output has no colors in shell (both Git Bash and Cygwin) [regression > in Jansi 1.16 / Maven 3.5.1] > - > > Key: MNG-6282 > URL: https://issues.apache.org/jira/browse/MNG-6282 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.5.1 >Reporter: Dejan Stojadinović > Labels: regression, windows > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > screenshot-4.png, screenshot-5-Cygwin.png, screenshot-6.png, screenshot-7.png > > > See > [screenshot|https://issues.apache.org/jira/secure/attachment/12886398/screenshot-1.png] > for more details. > _*Environment:*_ > * Windows 10, 64 bit > * Oracle Java, version: *1.8.0_144* > * Git Bash shell (MINGW64), Cygwin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169259#comment-16169259
]
Brian Oxley commented on MNG-6242:
--
Ah, just so. Were the passthrough flag to be added, it would be with a uname
check for Cygwin.
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Priority: Minor
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MJMOD-5) Usage of moduleName in describe/list goal / classpath usage in create goal
Karl Heinz Marbaise created MJMOD-5:
---
Summary: Usage of moduleName in describe/list goal / classpath
usage in create goal
Key: MJMOD-5
URL: https://issues.apache.org/jira/browse/MJMOD-5
Project: Maven JMod Plugin
Issue Type: Improvement
Affects Versions: 3.0.0-alpha-1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Priority: Blocker
Fix For: 3.0.0-alpha-1
The {{create}} goal uses classpath which should be prevented and replaced.
The {{list}} and {{describe}} goals using {{moduleName}} which is misleading
cause we only use the name of the jmod file. Not related to a module name in
any way.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (MJMOD-5) Usage of moduleName in describe/list goal / classpath usage in create goal
[
https://issues.apache.org/jira/browse/MJMOD-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MJMOD-5.
---
Resolution: Fixed
Done in [r1808613|https://svn.apache.org/r1808613]
> Usage of moduleName in describe/list goal / classpath usage in create goal
> --
>
> Key: MJMOD-5
> URL: https://issues.apache.org/jira/browse/MJMOD-5
> Project: Maven JMod Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
>
> The {{create}} goal uses classpath which should be prevented and replaced.
> The {{list}} and {{describe}} goals using {{moduleName}} which is misleading
> cause we only use the name of the jmod file. Not related to a module name in
> any way.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MJMOD-5) Usage of moduleName in describe/list goal / classpath usage in create goal
[
https://issues.apache.org/jira/browse/MJMOD-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169265#comment-16169265
]
Hudson commented on MJMOD-5:
SUCCESS: Integrated in Jenkins build maven-plugins #9139 (See
[https://builds.apache.org/job/maven-plugins/9139/])
[MJMOD-5] Usage of moduleName in describe/list goal / classpath usage in create
goal
o in describe/list goal change the moduleName into jmodFile using
a default or can be given explicit by a property.
Added IT's for direct call of the goals describe/list.
o Removed the parameter classPath from the goal create. The command line
will got the information from pathElements instead. (khmarbaise:
[http://svn.apache.org/viewvc/?view=rev&rev=1808613])
* (add) maven-jmod-plugin/src/it/describe-plain
* (add) maven-jmod-plugin/src/it/describe-plain/invoker.properties
* (add) maven-jmod-plugin/src/it/describe-plain/pom.xml
* (add) maven-jmod-plugin/src/it/describe-plain/src
* (add) maven-jmod-plugin/src/it/describe-plain/src/main
* (add) maven-jmod-plugin/src/it/describe-plain/src/main/configs
* (add) maven-jmod-plugin/src/it/describe-plain/src/main/configs/config.test
* (add) maven-jmod-plugin/src/it/describe-plain/src/main/java
* (add) maven-jmod-plugin/src/it/describe-plain/src/main/java/module-info.java
* (add) maven-jmod-plugin/src/it/describe-plain/src/main/java/myproject
* (add)
maven-jmod-plugin/src/it/describe-plain/src/main/java/myproject/HelloWorld.java
* (add) maven-jmod-plugin/src/it/describe-plain/verify.groovy
* (add) maven-jmod-plugin/src/it/list-plain
* (add) maven-jmod-plugin/src/it/list-plain/invoker.properties
* (add) maven-jmod-plugin/src/it/list-plain/pom.xml
* (add) maven-jmod-plugin/src/it/list-plain/src
* (add) maven-jmod-plugin/src/it/list-plain/src/main
* (add) maven-jmod-plugin/src/it/list-plain/src/main/configs
* (add) maven-jmod-plugin/src/it/list-plain/src/main/configs/config.test
* (add) maven-jmod-plugin/src/it/list-plain/src/main/java
* (add) maven-jmod-plugin/src/it/list-plain/src/main/java/module-info.java
* (add) maven-jmod-plugin/src/it/list-plain/src/main/java/myproject
* (add)
maven-jmod-plugin/src/it/list-plain/src/main/java/myproject/HelloWorld.java
* (add) maven-jmod-plugin/src/it/list-plain/verify.groovy
* (edit)
maven-jmod-plugin/src/main/java/org/apache/maven/plugins/jmod/JModCreateMojo.java
* (edit)
maven-jmod-plugin/src/main/java/org/apache/maven/plugins/jmod/JModDescribeMojo.java
* (edit)
maven-jmod-plugin/src/main/java/org/apache/maven/plugins/jmod/JModListMojo.java
> Usage of moduleName in describe/list goal / classpath usage in create goal
> --
>
> Key: MJMOD-5
> URL: https://issues.apache.org/jira/browse/MJMOD-5
> Project: Maven JMod Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
>
> The {{create}} goal uses classpath which should be prevented and replaced.
> The {{list}} and {{describe}} goals using {{moduleName}} which is misleading
> cause we only use the name of the jmod file. Not related to a module name in
> any way.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169266#comment-16169266
]
Brian Oxley commented on MNG-6242:
--
To be specific:
{noformat}
*$ diff mvn-original mvn
183a184,189
> if $cygwin || $mingw; then
> if [ -t 1 ]; then
> MAVEN_OPTS="-Djansi.passthrough=true $MAVEN_OPTS"
> fi
> fi
>
{noformat}
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Priority: Minor
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SUREFIRE-1419) ForkStarter throws exception
Brian Oxley created SUREFIRE-1419:
-
Summary: ForkStarter throws exception
Key: SUREFIRE-1419
URL: https://issues.apache.org/jira/browse/SUREFIRE-1419
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.20.1
Environment: Cygwin
Reporter: Brian Oxley
In this project, surefire/failsafe 2.20 work with warnings; with 2.20.1 they
die with exceptions:
https://github.com/binkley/sproingk
The stack trace:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
project sproingk: There are test failures.
[ERROR]
[ERROR] Please refer to
C:\cygwin64\home\binkl\src\kt\sproingk\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] There was an error in the forked process
[ERROR]
org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There was
an error in the forked process
[ERROR]
org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:673)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
[ERROR] at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
[ERROR] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
[ERROR] at
org.apache.maven.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:39)
[ERROR] at
org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:122)
[ERROR] at
org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:50)
[ERROR]
[ERROR] -> [Help
[jira] [Commented] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169344#comment-16169344
]
Hervé Boutemy commented on MNG-6242:
ok, I didn't remember these {{$cygwin}} and {{$mingw}} variables that were
available in {{mvn}} shell script: ok, if I need to code a workaround for Maven
3.5.2, I buy your implementation :)
thanks for the detailed hint
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Priority: Minor
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MEAR-249) Maven EAR plugin - two libraries with a same ArtifactId
[ https://issues.apache.org/jira/browse/MEAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169345#comment-16169345 ] Tomas Tulka commented on MEAR-249: -- This solution is okay for me, I was just wandering if it wouldn't be possible to generate the full name mapping automatically in this case, or to create an indexing for the same artifact files, something like `same-artifact.jar` and `same-artifact (1).jar` in the example above. The point here is, there is nothing wrong with the artifacts, everything is valid and a wrong result is generated. It means ERROR is inappropriate here. But the WARNING with the hint is probably sufficient enough. Thank you! > Maven EAR plugin - two libraries with a same ArtifactId > --- > > Key: MEAR-249 > URL: https://issues.apache.org/jira/browse/MEAR-249 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: waiting-for-feedback >Reporter: Tomas Tulka > > When an EAR module has two (or more) dependencies with a same artifactId, > Maven copy those into the /lib directory and one rewrites the other. In the > end there is only one library in the EAR. > This is not what I would expect, because it is correct to have such > dependencies. The plugin should deal with it or print a warning (it's a > tricky issue when it is about transitive dependencies). > > com.group1 > same-artifact > > > com.group2 > same-artifact > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6242:
---
Fix Version/s: 3.5.2-candidate
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Priority: Minor
> Fix For: 3.5.2-candidate
>
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169344#comment-16169344
]
Hervé Boutemy edited comment on MNG-6242 at 9/17/17 4:40 PM:
-
ok, I:
- didn't remember these {{$cygwin}} and {{$mingw}} variables that were
available in {{mvn}} shell script
- didn't think about the {{test -t DESCRIPTOR}} to detect terminal
ok, if I need to code a workaround for Maven 3.5.2, I buy your implementation
which is perfect :)
thanks for the detailed hint
was (Author: hboutemy):
ok, I didn't remember these {{$cygwin}} and {{$mingw}} variables that were
available in {{mvn}} shell script: ok, if I need to code a workaround for Maven
3.5.2, I buy your implementation :)
thanks for the detailed hint
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Priority: Minor
> Fix For: 3.5.2-candidate
>
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169344#comment-16169344
]
Hervé Boutemy edited comment on MNG-6242 at 9/17/17 4:41 PM:
-
ok, I:
- didn't remember these {{$cygwin}} and {{$mingw}} variables that were
available in {{mvn}} shell script
- didn't think about the {{test -t DESCRIPTOR}} to detect terminal
ok, if I need to code a workaround for Maven 3.5.2, I buy your implementation
which is perfect :)
thanks for the detailed hint
was (Author: hboutemy):
ok, I:
- didn't remember these {{$cygwin}} and {{$mingw}} variables that were
available in {{mvn}} shell script
- didn't think about the {{test -t DESCRIPTOR}} to detect terminal
ok, if I need to code a workaround for Maven 3.5.2, I buy your implementation
which is perfect :)
thanks for the detailed hint
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Priority: Minor
> Fix For: 3.5.2-candidate
>
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MEAR-249) Maven EAR plugin - two libraries with a same ArtifactId
[ https://issues.apache.org/jira/browse/MEAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169352#comment-16169352 ] Karl Heinz Marbaise commented on MEAR-249: -- Hi, first thanks for your feedback. yes this was right and the wrong result was generated which is based on the previous wrong implementation. The thing is if a user decided to define a different mapping (which is now no problem with the new implementation) which would clash in names (same file name) there should be an error cause otherwise it would not being fixed and would produce wrong results in the resulting EAR file...(which means overwriting of existing files!).. > Maven EAR plugin - two libraries with a same ArtifactId > --- > > Key: MEAR-249 > URL: https://issues.apache.org/jira/browse/MEAR-249 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: waiting-for-feedback >Reporter: Tomas Tulka > > When an EAR module has two (or more) dependencies with a same artifactId, > Maven copy those into the /lib directory and one rewrites the other. In the > end there is only one library in the EAR. > This is not what I would expect, because it is correct to have such > dependencies. The plugin should deal with it or print a warning (it's a > tricky issue when it is about transitive dependencies). > > com.group1 > same-artifact > > > com.group2 > same-artifact > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1389) Java package regex via command line selects no tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169396#comment-16169396
]
Tibor Digana commented on SUREFIRE-1389:
[~elserj]
Your problem is that you think this is Ant regex
{{-Dtest='org.apache.hadoop.hbase.quotas.*'}}.
Try this {{-Dtest=%regex[org.apache.hadoop.hbase.quotas.*]}} and do not use
simple quotation marks.
> Java package regex via command line selects no tests
>
>
> Key: SUREFIRE-1389
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1389
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Josh Elser
>Assignee: Tibor Digana
>
> We noticed the following problem over in
> [HBase|https://issues.apache.org/jira/browse/HBASE-18264?focusedCommentId=16082795&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16082795]
> On surefire 2.18.1 and 2.19.1, the following command would have the effect of
> running all tests which exist in the package
> {{org.apache.hadoop.hbase.quotas}}:
> {noformat}
> mvn package -Dtest='org.apache.hadoop.hbase.quotas.*'
> {noformat}
> Upon upgrading to 2.20, the same command executes no tests.
> If helpful, plugin configuration (albeit convoluted) can be found at
> https://github.com/apache/hbase/blob/branch-2/pom.xml. Happy to provide other
> info to help debug further -- I haven't tried a trivial reproduction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1
[
https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169409#comment-16169409
]
Tibor Digana commented on SUREFIRE-1397:
[~piotr.krokow...@sabre.com]
Take a look into class {{AbstractSurefireMojo.java}} and you will see no race
condition because there is no parallelism.
I think this is JDK issue.
What version and vendor of JDK you use?
> "ExecutionException Cannot create workingDirectory" occurs randomly when
> forkCount>1
>
>
> Key: SUREFIRE-1397
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1397
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19, 2.19.1, 2.20
>Reporter: Piotr Krokowski
>Assignee: Tibor Digana
> Attachments: debug-output.txt, pom.xml
>
>
> I've verified the same scenario with 2.18, 2.19 and 2.20 versions of the
> plugin.
> It looks like the issue was introduced in 2.19.
> I'd kindly like to ask to fix this as soon as possible, as this is a blocker
> in adopting JUnit5!
> Steps to reproduce:
> - Have a simple project with at least two tests
> - Configure {code}forkCount=2{code}
> - Configure workingDirectory, eg.
> {code}${project.basedir}/target/test-run{code}
> - Run {code}mvn clean test -T 2{code}
> - Observe the exception (might occur randomly)
> I'm attaching the error message, full stack trace, and my example pom.xml,
> that I used to reproduce the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1
[
https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169418#comment-16169418
]
Tibor Digana commented on SUREFIRE-1397:
[~piotr.krokow...@sabre.com]
I used your POM and added {{ATest.java}} with versions {{2.19.1}}, {{2.20}},
{{2.20.1}} and the folder was always created {{target/test-run}} with my
command {{mvn clean test -T 2}} .
{{mvn --version}}
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T18:37:52+01:00)
Maven home: D:\apache-maven-3.2.1
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: e:\Program Files\Java\jdk1.8.0_144\jre
Default locale: en_US, platform encoding: Cp1250
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> "ExecutionException Cannot create workingDirectory" occurs randomly when
> forkCount>1
>
>
> Key: SUREFIRE-1397
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1397
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19, 2.19.1, 2.20
>Reporter: Piotr Krokowski
>Assignee: Tibor Digana
> Attachments: debug-output.txt, pom.xml
>
>
> I've verified the same scenario with 2.18, 2.19 and 2.20 versions of the
> plugin.
> It looks like the issue was introduced in 2.19.
> I'd kindly like to ask to fix this as soon as possible, as this is a blocker
> in adopting JUnit5!
> Steps to reproduce:
> - Have a simple project with at least two tests
> - Configure {code}forkCount=2{code}
> - Configure workingDirectory, eg.
> {code}${project.basedir}/target/test-run{code}
> - Run {code}mvn clean test -T 2{code}
> - Observe the exception (might occur randomly)
> I'm attaching the error message, full stack trace, and my example pom.xml,
> that I used to reproduce the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1418) 2.20.1 fails with no tests and junit5 support
[
https://issues.apache.org/jira/browse/SUREFIRE-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169424#comment-16169424
]
Tibor Digana commented on SUREFIRE-1418:
Yes, JUnit5 must adapt the provider.
You should contact Marc Philipp in Github Junit-Team. We have one developer,
Benedikt Ritter, who works on provider in Surefire team. We plan to have the
provider fully adopted in Surefire sources in the first release 3.0.0. I think
Benedikt is in progress with the provider and he was working on
{{AbstractSurefireMojo}} last time. I will ask him about the status.
So now I am closing. If you see any problem with that we can discuss it.
When I run empty project with Surefire {{2.20.1}} I get no error:
[INFO] --- maven-surefire-plugin:2.20:test (default-test) @ test ---
[INFO] No tests to run.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.366 s (Wall Clock)
[INFO] Finished at: 2017-09-17T23:22:54+01:00
[INFO] Final Memory: 8M/309M
[INFO]
> 2.20.1 fails with no tests and junit5 support
> -
>
> Key: SUREFIRE-1418
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1418
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T20:39:06+01:00)
> Maven home: /opt/local/share/java/maven3
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: John Patrick
> Attachments: effective-pom.xml, output.txt
>
>
> Just upgraded project from 2.20 to 2.20.1 and getting error for a project
> with no tests.
> If you remove the following it will pass, otherwise it fails.
>
>
>
> org.junit.platform
>
> junit-platform-surefire-provider
> 1.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (SUREFIRE-1418) 2.20.1 fails with no tests and junit5 support
[ https://issues.apache.org/jira/browse/SUREFIRE-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1418. -- Resolution: Not A Bug Assignee: Tibor Digana > 2.20.1 fails with no tests and junit5 support > - > > Key: SUREFIRE-1418 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1418 > Project: Maven Surefire > Issue Type: Bug > Components: JUnit 5.x support, Maven Surefire Plugin >Affects Versions: 2.20.1 > Environment: Apache Maven 3.5.0 > (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T20:39:06+01:00) > Maven home: /opt/local/share/java/maven3 > Java version: 1.8.0_131, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac" >Reporter: John Patrick >Assignee: Tibor Digana > Attachments: effective-pom.xml, output.txt > > > Just upgraded project from 2.20 to 2.20.1 and getting error for a project > with no tests. > If you remove the following it will pass, otherwise it fails. > > > > org.junit.platform > > junit-platform-surefire-provider > 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SUREFIRE-1419) ForkStarter throws exception
[
https://issues.apache.org/jira/browse/SUREFIRE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1419:
--
Assignee: Tibor Digana
> ForkStarter throws exception
>
>
> Key: SUREFIRE-1419
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1419
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Cygwin
>Reporter: Brian Oxley
>Assignee: Tibor Digana
>
> In this project, surefire/failsafe 2.20 work with warnings; with 2.20.1 they
> die with exceptions:
> https://github.com/binkley/sproingk
> The stack trace:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project sproingk: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\cygwin64\home\binkl\src\kt\sproingk\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] There was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There
> was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:673)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ER
[jira] [Commented] (SUREFIRE-1419) ForkStarter throws exception
[
https://issues.apache.org/jira/browse/SUREFIRE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169434#comment-16169434
]
Tibor Digana commented on SUREFIRE-1419:
[~binkley]
Go to {{target/surefire-reports}} and you will see trace.
This is related to JUnit5. I had to breaks backwards compatibility and we have
to do it in next few versions ({{2.21.0.Jigsaw}} and {{2.21.2}}) due to fixing
the bugs requires me to do.
Please adapt JUnit5 Surefire Provider
# Created on 2017-09-17T23:46:02.635
java.lang.NoSuchMethodError:
org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
at
org.junit.platform.surefire.provider.JUnitPlatformProvider.invokeSingleClass(JUnitPlatformProvider.java:137)
at
org.junit.platform.surefire.provider.JUnitPlatformProvider.invokeAllTests(JUnitPlatformProvider.java:126)
at
org.junit.platform.surefire.provider.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:105)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:373)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:334)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:119)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:407)
> ForkStarter throws exception
>
>
> Key: SUREFIRE-1419
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1419
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Cygwin
>Reporter: Brian Oxley
>Assignee: Tibor Digana
>
> In this project, surefire/failsafe 2.20 work with warnings; with 2.20.1 they
> die with exceptions:
> https://github.com/binkley/sproingk
> The stack trace:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project sproingk: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\cygwin64\home\binkl\src\kt\sproingk\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] There was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There
> was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:673)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.j
[jira] [Commented] (SUREFIRE-1419) ForkStarter throws exception
[
https://issues.apache.org/jira/browse/SUREFIRE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169436#comment-16169436
]
Tibor Digana commented on SUREFIRE-1419:
The signature
{{org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V}}
changed to
{{org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/TestSetReportEntry;)V}}
And the same happened with method {{testSetCompleted}}.
> ForkStarter throws exception
>
>
> Key: SUREFIRE-1419
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1419
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Cygwin
>Reporter: Brian Oxley
>Assignee: Tibor Digana
>
> In this project, surefire/failsafe 2.20 work with warnings; with 2.20.1 they
> die with exceptions:
> https://github.com/binkley/sproingk
> The stack trace:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project sproingk: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\cygwin64\home\binkl\src\kt\sproingk\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] There was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There
> was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:673)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds
[jira] [Commented] (SUREFIRE-1418) 2.20.1 fails with no tests and junit5 support
[
https://issues.apache.org/jira/browse/SUREFIRE-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169437#comment-16169437
]
Tibor Digana commented on SUREFIRE-1418:
The signature
{{org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V}}
changed to
{{org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/TestSetReportEntry;)V}}
And the same happened with method {{testSetCompleted}}.
> 2.20.1 fails with no tests and junit5 support
> -
>
> Key: SUREFIRE-1418
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1418
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T20:39:06+01:00)
> Maven home: /opt/local/share/java/maven3
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: John Patrick
>Assignee: Tibor Digana
> Attachments: effective-pom.xml, output.txt
>
>
> Just upgraded project from 2.20 to 2.20.1 and getting error for a project
> with no tests.
> If you remove the following it will pass, otherwise it fails.
>
>
>
> org.junit.platform
>
> junit-platform-surefire-provider
> 1.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (SUREFIRE-1419) ForkStarter throws exception
[
https://issues.apache.org/jira/browse/SUREFIRE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1419.
--
Resolution: Duplicate
> ForkStarter throws exception
>
>
> Key: SUREFIRE-1419
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1419
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Cygwin
>Reporter: Brian Oxley
>Assignee: Tibor Digana
> Labels: junit5
>
> In this project, surefire/failsafe 2.20 work with warnings; with 2.20.1 they
> die with exceptions:
> https://github.com/binkley/sproingk
> The stack trace:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project sproingk: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\cygwin64\home\binkl\src\kt\sproingk\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] There was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There
> was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:673)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
[jira] [Updated] (SUREFIRE-1418) 2.20.1 fails with no tests and junit5 support
[ https://issues.apache.org/jira/browse/SUREFIRE-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1418: --- Labels: junit5 (was: ) > 2.20.1 fails with no tests and junit5 support > - > > Key: SUREFIRE-1418 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1418 > Project: Maven Surefire > Issue Type: Bug > Components: JUnit 5.x support, Maven Surefire Plugin >Affects Versions: 2.20.1 > Environment: Apache Maven 3.5.0 > (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T20:39:06+01:00) > Maven home: /opt/local/share/java/maven3 > Java version: 1.8.0_131, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac" >Reporter: John Patrick >Assignee: Tibor Digana > Labels: junit5 > Attachments: effective-pom.xml, output.txt > > > Just upgraded project from 2.20 to 2.20.1 and getting error for a project > with no tests. > If you remove the following it will pass, otherwise it fails. > > > > org.junit.platform > > junit-platform-surefire-provider > 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1419) ForkStarter throws exception
[
https://issues.apache.org/jira/browse/SUREFIRE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1419:
---
Labels: junit5 (was: )
> ForkStarter throws exception
>
>
> Key: SUREFIRE-1419
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1419
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Cygwin
>Reporter: Brian Oxley
>Assignee: Tibor Digana
> Labels: junit5
>
> In this project, surefire/failsafe 2.20 work with warnings; with 2.20.1 they
> die with exceptions:
> https://github.com/binkley/sproingk
> The stack trace:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project sproingk: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\cygwin64\home\binkl\src\kt\sproingk\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] There was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There
> was an error in the forked process
> [ERROR]
> org.apache.maven.surefire.report.RunListener.testSetStarting(Lorg/apache/maven/surefire/report/ReportEntry;)V
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:673)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
[jira] [Commented] (SUREFIRE-1389) Java package regex via command line selects no tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169486#comment-16169486
]
Josh Elser commented on SUREFIRE-1389:
--
bq. do not use simple quotation marks
This was to work around my shell expanding the asterisk instead of passing it
along. I can escape it instead.
Did I miss some release notes where this functionality changed? Or, was this
just something that previously happened to work but was never intended to work?
> Java package regex via command line selects no tests
>
>
> Key: SUREFIRE-1389
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1389
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Josh Elser
>Assignee: Tibor Digana
>
> We noticed the following problem over in
> [HBase|https://issues.apache.org/jira/browse/HBASE-18264?focusedCommentId=16082795&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16082795]
> On surefire 2.18.1 and 2.19.1, the following command would have the effect of
> running all tests which exist in the package
> {{org.apache.hadoop.hbase.quotas}}:
> {noformat}
> mvn package -Dtest='org.apache.hadoop.hbase.quotas.*'
> {noformat}
> Upon upgrading to 2.20, the same command executes no tests.
> If helpful, plugin configuration (albeit convoluted) can be found at
> https://github.com/apache/hbase/blob/branch-2/pom.xml. Happy to provide other
> info to help debug further -- I haven't tried a trivial reproduction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1389) Java package regex via command line selects no tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169491#comment-16169491
]
Tibor Digana commented on SUREFIRE-1389:
[~elserj]
The documentation did not change. It was never intended to work in any other
version. The implementation is more strict since version {{2.19}}. In Surefire
{{3.0}}, see SUREFIRE-1309, I want to break backwards compatibility and use
normal fully qualified class name in regex instead.
> Java package regex via command line selects no tests
>
>
> Key: SUREFIRE-1389
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1389
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Josh Elser
>Assignee: Tibor Digana
>
> We noticed the following problem over in
> [HBase|https://issues.apache.org/jira/browse/HBASE-18264?focusedCommentId=16082795&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16082795]
> On surefire 2.18.1 and 2.19.1, the following command would have the effect of
> running all tests which exist in the package
> {{org.apache.hadoop.hbase.quotas}}:
> {noformat}
> mvn package -Dtest='org.apache.hadoop.hbase.quotas.*'
> {noformat}
> Upon upgrading to 2.20, the same command executes no tests.
> If helpful, plugin configuration (albeit convoluted) can be found at
> https://github.com/apache/hbase/blob/branch-2/pom.xml. Happy to provide other
> info to help debug further -- I haven't tried a trivial reproduction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
