date:20171002

[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

2017-10-02 Thread Emmanuel Bourg (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189019#comment-16189019
 ] 

Emmanuel Bourg commented on SUREFIRE-1422:
--

Thank you Tibor, I haven't tried yet but the commit looks good.

> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
> Fix For: 2.21.0.Jigsaw
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure 
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test 
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that 
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on 
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at 
> least check its existence and display an explicit message stating that it 
> must be installed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MCHECKSTYLE-342) Support XML 1.1

2017-10-02 Thread richard (JIRA)


 [ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

richard updated MCHECKSTYLE-342:

Description: 
Checkstyle wishes to upgrade our XML logger to print out XML 1.1 documents. We 
need this functionality to support escaping non-printable characters as XML 1.0 
doesn't allow this and considers it an invalid document.
> Exception in thread "main" javax.xml.stream.XMLStreamException: ParseError at 
> [row,col]:[45615,80]
> Message: An invalid XML character (Unicode: 0x2) was found in the value of 
> attribute "message" and element is "error".

Checkstyle cannot upgrade until maven-checkstyle does as we use it in alot of 
regression testing. If we try to give the plugin an XML 1.1 document, it fails 
with the following error:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
> project postgresql: Unable to read Checkstyle results xml: 
> /pipeline/source/pgjdbc/pgjdbc/target/checkstyle-result.xml: only 1.0 is 
> supported as  version="1.1"... @1:19) -> [Help 1]

  was:
Checkstyle wishes to upgrade our XML logger to print out XML 1.1 documents. We 
need this functionality to support escaping non-printable characters as XML 1.0 
doesn't allow this and considers it an invalid document.
Exception in thread "main" javax.xml.stream.XMLStreamException: ParseError at 
[row,col]:[45615,80]
Message: An invalid XML character (Unicode: 0x2) was found in the value of 
attribute "message" and element is "error".

Checkstyle cannot upgrade until maven-checkstyle does as we use it in alot of 
regression testing. If we try to give the plugin an XML 1.1 document, it fails 
with the following error:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
> project postgresql: Unable to read Checkstyle results xml: 
> /pipeline/source/pgjdbc/pgjdbc/target/checkstyle-result.xml: only 1.0 is 
> supported as  version="1.1"... @1:19) -> [Help 1]


> Support XML 1.1
> ---
>
> Key: MCHECKSTYLE-342
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-342
> Project: Maven Checkstyle Plugin
>  Issue Type: New Feature
>  Components: checkstyle:check
>Affects Versions: 2.17
>Reporter: richard
>
> Checkstyle wishes to upgrade our XML logger to print out XML 1.1 documents. 
> We need this functionality to support escaping non-printable characters as 
> XML 1.0 doesn't allow this and considers it an invalid document.
> > Exception in thread "main" javax.xml.stream.XMLStreamException: ParseError 
> > at [row,col]:[45615,80]
> > Message: An invalid XML character (Unicode: 0x2) was found in the value of 
> > attribute "message" and element is "error".
> Checkstyle cannot upgrade until maven-checkstyle does as we use it in alot of 
> regression testing. If we try to give the plugin an XML 1.1 document, it 
> fails with the following error:
> > [ERROR] Failed to execute goal 
> > org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) 
> > on project postgresql: Unable to read Checkstyle results xml: 
> > /pipeline/source/pgjdbc/pgjdbc/target/checkstyle-result.xml: only 1.0 is 
> > supported as  > version="1.1"... @1:19) -> [Help 1]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MCHECKSTYLE-342) Support XML 1.1

2017-10-02 Thread richard (JIRA)

richard created MCHECKSTYLE-342:
---

 Summary: Support XML 1.1
 Key: MCHECKSTYLE-342
 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-342
 Project: Maven Checkstyle Plugin
  Issue Type: New Feature
  Components: checkstyle:check
Affects Versions: 2.17
Reporter: richard


Checkstyle wishes to upgrade our XML logger to print out XML 1.1 documents. We 
need this functionality to support escaping non-printable characters as XML 1.0 
doesn't allow this and considers it an invalid document.
> Exception in thread "main" javax.xml.stream.XMLStreamException: ParseError at 
> [row,col]:[45615,80]
> Message: An invalid XML character (Unicode: 0x2) was found in the value of 
> attribute "message" and element is "error".

Checkstyle cannot upgrade until maven-checkstyle does as we use it in alot of 
regression testing. If we try to give the plugin an XML 1.1 document, it fails 
with the following error:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
> project postgresql: Unable to read Checkstyle results xml: 
> /pipeline/source/pgjdbc/pgjdbc/target/checkstyle-result.xml: only 1.0 is 
> supported as  version="1.1"... @1:19) -> [Help 1]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MCHECKSTYLE-342) Support XML 1.1

2017-10-02 Thread richard (JIRA)


 [ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

richard updated MCHECKSTYLE-342:

Description: 
Checkstyle wishes to upgrade our XML logger to print out XML 1.1 documents. We 
need this functionality to support escaping non-printable characters as XML 1.0 
doesn't allow this and considers it an invalid document.
Exception in thread "main" javax.xml.stream.XMLStreamException: ParseError at 
[row,col]:[45615,80]
Message: An invalid XML character (Unicode: 0x2) was found in the value of 
attribute "message" and element is "error".

Checkstyle cannot upgrade until maven-checkstyle does as we use it in alot of 
regression testing. If we try to give the plugin an XML 1.1 document, it fails 
with the following error:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
> project postgresql: Unable to read Checkstyle results xml: 
> /pipeline/source/pgjdbc/pgjdbc/target/checkstyle-result.xml: only 1.0 is 
> supported as  version="1.1"... @1:19) -> [Help 1]

  was:
Checkstyle wishes to upgrade our XML logger to print out XML 1.1 documents. We 
need this functionality to support escaping non-printable characters as XML 1.0 
doesn't allow this and considers it an invalid document.
> Exception in thread "main" javax.xml.stream.XMLStreamException: ParseError at 
> [row,col]:[45615,80]
> Message: An invalid XML character (Unicode: 0x2) was found in the value of 
> attribute "message" and element is "error".

Checkstyle cannot upgrade until maven-checkstyle does as we use it in alot of 
regression testing. If we try to give the plugin an XML 1.1 document, it fails 
with the following error:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
> project postgresql: Unable to read Checkstyle results xml: 
> /pipeline/source/pgjdbc/pgjdbc/target/checkstyle-result.xml: only 1.0 is 
> supported as  version="1.1"... @1:19) -> [Help 1]


> Support XML 1.1
> ---
>
> Key: MCHECKSTYLE-342
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-342
> Project: Maven Checkstyle Plugin
>  Issue Type: New Feature
>  Components: checkstyle:check
>Affects Versions: 2.17
>Reporter: richard
>
> Checkstyle wishes to upgrade our XML logger to print out XML 1.1 documents. 
> We need this functionality to support escaping non-printable characters as 
> XML 1.0 doesn't allow this and considers it an invalid document.
> Exception in thread "main" javax.xml.stream.XMLStreamException: ParseError at 
> [row,col]:[45615,80]
> Message: An invalid XML character (Unicode: 0x2) was found in the value of 
> attribute "message" and element is "error".
> Checkstyle cannot upgrade until maven-checkstyle does as we use it in alot of 
> regression testing. If we try to give the plugin an XML 1.1 document, it 
> fails with the following error:
> > [ERROR] Failed to execute goal 
> > org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) 
> > on project postgresql: Unable to read Checkstyle results xml: 
> > /pipeline/source/pgjdbc/pgjdbc/target/checkstyle-result.xml: only 1.0 is 
> > supported as  > version="1.1"... @1:19) -> [Help 1]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SUREFIRE-1426) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true

2017-10-02 Thread Dan Berindei (JIRA)


 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Berindei updated SUREFIRE-1426:
---
Attachment: surefire-1426-test.tar.gz

[~tibor17] maybe I wasn't clear, but when surefire logs the {{Unable to load 
category: stress}} error, it doesn't run any tests in that module. You can 
reproduce it by running {{mvn test -Dmaven.test.failure.ignore=true}} in the 
attached reactor project, 

I don't want any reactor-level features, like SUREFIRE-1142 proposes, although 
it is an interesting proposal. I just want the module build to either a) finish 
writing the test execution reports or b) stop the build.


> Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true
> ---
>
> Key: SUREFIRE-1426
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1426
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Reporter: Dan Berindei
>Assignee: Tibor Digana
> Attachments: surefire-1426-test.tar.gz
>
>
> We have a reactor with many modules, and also a few random test failures. We 
> want to run the tests of all the modules even if a test failed in the core 
> module, so we use {{mvn -Dmaven.test.failure.ignore=true}}. {{mvn 
> --fail-at-end}} only builds the modules that do not depend on the module with 
> a failed test.
> The problem is that fork crashes like this one are written to the surefire 
> reports, so Jenkins ignores them:
> {noformat}
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> Unable to load category: stress
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:665)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356){noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (SUREFIRE-1426) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true

2017-10-02 Thread Dan Berindei (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188372#comment-16188372
 ] 

Dan Berindei edited comment on SUREFIRE-1426 at 10/2/17 4:17 PM:
-

[~tibor17] maybe I wasn't clear, but when surefire logs the {{Unable to load 
category: stress}} error, it doesn't run any tests in that module. You can 
reproduce it by running {{mvn test -Dmaven.test.failure.ignore=true}} in the 
attached reactor project, 

I don't want any reactor-level features like SUREFIRE-1142, although it is an 
interesting proposal. I just want the module build to either a) finish writing 
the test execution reports or b) stop the build.



was (Author: dan.berindei):
[~tibor17] maybe I wasn't clear, but when surefire logs the {{Unable to load 
category: stress}} error, it doesn't run any tests in that module. You can 
reproduce it by running {{mvn test -Dmaven.test.failure.ignore=true}} in the 
attached reactor project, 

I don't want any reactor-level features, like SUREFIRE-1142 proposes, although 
it is an interesting proposal. I just want the module build to either a) finish 
writing the test execution reports or b) stop the build.


> Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true
> ---
>
> Key: SUREFIRE-1426
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1426
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Reporter: Dan Berindei
>Assignee: Tibor Digana
> Attachments: surefire-1426-test.tar.gz
>
>
> We have a reactor with many modules, and also a few random test failures. We 
> want to run the tests of all the modules even if a test failed in the core 
> module, so we use {{mvn -Dmaven.test.failure.ignore=true}}. {{mvn 
> --fail-at-end}} only builds the modules that do not depend on the module with 
> a failed test.
> The problem is that fork crashes like this one are written to the surefire 
> reports, so Jenkins ignores them:
> {noformat}
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> Unable to load category: stress
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:665)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>

[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed

2017-10-02 Thread Mark Raynsford (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188337#comment-16188337
 ] 

Mark Raynsford commented on MDEP-559:
-

Hello!

Unfortunately, it's still broken with ASM 6.0, but broken in a new way:

`Caused by: java.lang.RuntimeException: Unknown constant pool type`

See the repro case and full exception log here:

https://github.com/io7m/maven-dependency-plugin-20171002

Just "mvn verify"

> Java 9 bytecode cannot be parsed
> 
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9 
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @ 
> lmdbjava ---
> [DEBUG] Configuring mojo 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from 
> plugin realm 
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0, 
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo 
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with 
> basic configurator -->
> [DEBUG]   (f) analyzer = default
> [DEBUG]   (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG]   (f) failOnWarning = true
> [DEBUG]   (f) ignoreNonCompile = false
> [DEBUG]   (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG]   (f) outputXML = false
> [DEBUG]   (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @ 
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG]   (f) scriptableFlag = $$%%%
> [DEBUG]   (f) scriptableOutput = false
> [DEBUG]   (f) skip = false
> [DEBUG]   (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64, 
> org.lmdbjava:lmdbjava-native-windows-x86_64, 
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG]   (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 
> (config-dependency) on project lmdbjava: Execution config-dependency of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed. 
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 
> (config-dependency) on project lmdbjava: Execution config-dependency of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>   at org.apache.maven.cli.MavenCli.doMa

[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

2017-10-02 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188318#comment-16188318
 ] 

Tibor Digana commented on SUREFIRE-1422:


[~fgaule]
In your case it is not clear to me. The PS is installed and can be executed? 
Please check it!

> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
> Fix For: 2.21.0.Jigsaw
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure 
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test 
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that 
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on 
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at 
> least check its existence and display an explicit message stating that it 
> must be installed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

2017-10-02 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188307#comment-16188307
 ] 

Tibor Digana commented on SUREFIRE-1422:


[~ebourg]
Can you install the branch [1] via {{mvn install -DskipTests} and give it a try 
with version {{2.21.0-SNAPSHOT}}?
[1]: 
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=shortlog;h=refs/heads/SUREFIRE-1422

> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
> Fix For: 2.21.0.Jigsaw
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure 
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test 
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that 
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on 
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at 
> least check its existence and display an explicit message stating that it 
> must be installed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

2017-10-02 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188307#comment-16188307
 ] 

Tibor Digana edited comment on SUREFIRE-1422 at 10/2/17 3:17 PM:
-

[~ebourg]
Can you install the branch [1] via {{mvn install -DskipTests}} and give it a 
try with version {{2.21.0-SNAPSHOT}}?
[1]: 
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=shortlog;h=refs/heads/SUREFIRE-1422


was (Author: tibor17):
[~ebourg]
Can you install the branch [1] via {{mvn install -DskipTests} and give it a try 
with version {{2.21.0-SNAPSHOT}}?
[1]: 
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=shortlog;h=refs/heads/SUREFIRE-1422

> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
> Fix For: 2.21.0.Jigsaw
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure 
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test 
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that 
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on 
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at 
> least check its existence and display an explicit message stating that it 
> must be installed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1388) NullPointerException caused by DefaultReporterFactory.printTestFailures(DefaultReporterFactory.java:403)

2017-10-02 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188255#comment-16188255
 ] 

Tibor Digana commented on SUREFIRE-1388:


[~ruudp]
Would you provide me with a sample project to reproduce this issue with 
Surefire 2.20.1?
Thx.

> NullPointerException caused by 
> DefaultReporterFactory.printTestFailures(DefaultReporterFactory.java:403)
> 
>
> Key: SUREFIRE-1388
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1388
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19, 2.20
> Environment: Kotlin Spek
>Reporter: Ruud Paulissen
>Assignee: Tibor Digana
>  Labels: DefaultReporterFactory, NullPointerException
> Fix For: Backlog
>
> Attachments: pom kopie.xml, Schermafbeelding 2017-07-11 om 
> 09.59.23.png
>
>
> I'm trying to run Kotlin Spek tests (based on JUnit) from Maven. I've 
> followed the guide on their website, and can run the tests locally perfectly 
> fine.
> When I run the Maven "test" task however, some tests are annotated with 
> "FAILURE" in the output, with a plain "null" value appearing in the console. 
> Upon running "mvn test -e", I get the attached stack trace.
> I have attached my maven pom.xml file as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1426) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true

2017-10-02 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188222#comment-16188222
 ] 

Tibor Digana commented on SUREFIRE-1426:


[~dan.berindei]
If a fork crashes it usually does not mean an internal error. It might be test 
error or failure.
The system property {{maven.test.failure.ignore}} means that the build should 
succeed even if your test failed for any reason. This is a module related 
feature. It is not reactor related. 

Summary at the end of reactor does not exist at the moment and might be quite a 
nice feature to have in Maven but I think you have to ask in 
{{https://issues.apache.org/jira/browse/MNG}} directly. Is this issue a 
duplicate to [#SUREFIRE-1142] ?
If you are interested in this feature like deploy plugin has, you may have to 
see the code of {{maven-deploy-plugin}} and follow the parameter 
{{deployAtEnd}} and maybe this would be an inspiration for Surefire; or contact 
Andreas in SUREFIRE-1142 and finalize the feature together on GitHub.

> Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true
> ---
>
> Key: SUREFIRE-1426
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1426
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Reporter: Dan Berindei
>Assignee: Tibor Digana
>
> We have a reactor with many modules, and also a few random test failures. We 
> want to run the tests of all the modules even if a test failed in the core 
> module, so we use {{mvn -Dmaven.test.failure.ignore=true}}. {{mvn 
> --fail-at-end}} only builds the modules that do not depend on the module with 
> a failed test.
> The problem is that fork crashes like this one are written to the surefire 
> reports, so Jenkins ignores them:
> {noformat}
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> Unable to load category: stress
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:665)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356){noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1427) Surefire-plugin throws NoClassDefFoundError with static initialiser

2017-10-02 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188110#comment-16188110
 ] 

Tibor Digana commented on SUREFIRE-1427:


It's very hard to say, maybe you are missing a dependency for the class 
{{org.apache.axiom.om.OMFactory}}.
Can you provide me with a sample project to reproduce this issue?
Thx

> Surefire-plugin throws NoClassDefFoundError with static initialiser
> ---
>
> Key: SUREFIRE-1427
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1427
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
> Environment: jdk 1.8
> maven 3.3.3
>Reporter: Martin Gainty
>Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> when maven-surefire-plugin encounters static initialiser such as
> public class AxisDescription {
> org.apache.axiom.om.OMFactory omFactory = 
> org.apache.axiom.om.OMAbstractFactory.getOMFactory();
> //surefire throws NoClassDefFoundError on OMAbstractFactory ?!?!?
> //but if i remove static initialiser to wait until runtime to load 
> OMAbstractFactory it loads ok
> org.apache.axis2.description.AxisDescription:
>   public void setDocumentation(String documentation) {
> org.apache.axiom.om.OMFactory omFactory = 
> org.apache.axiom.om.OMAbstractFactory.getOMFactory();
> if (!"".equals(documentation)) {
> this.documentation = omFactory.createOMText(documentation);
> }
> }
> why does surefire not find classes referenced by static initialiser?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1426) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true

2017-10-02 Thread Dan Berindei (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188077#comment-16188077
 ] 

Dan Berindei commented on SUREFIRE-1426:


Sorry about that, let me try again...

First of all, "Unable to load category: stress" is an error in our surefire 
configuration, not a test failure, so it should fail the build, ignoring the 
{{maven.test.failure.ignore}} system property.

Going further, if a fork crashes while one or more tests are running I would 
also like surefire to ignore {{maven.test.failure.ignore}} and fail the build. 
However, it would also be ok if the build passed and the tests that were 
running at the time are marked as failed (and the tests that didn't run at all 
are marked as ignored) in the surefire reports. 

Basically I want fork errors to always be visible at the end of the reactor 
build, either as a non-zero exit code or as a {{}} tag in the reports. 
Currently a fork error means no reports are written, and with 
{{-Dmaven.test.failure.ignore=true}} the only way to find the failure is to 
scan the output of each module in the reactor.

> Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true
> ---
>
> Key: SUREFIRE-1426
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1426
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Reporter: Dan Berindei
>Assignee: Tibor Digana
>
> We have a reactor with many modules, and also a few random test failures. We 
> want to run the tests of all the modules even if a test failed in the core 
> module, so we use {{mvn -Dmaven.test.failure.ignore=true}}. {{mvn 
> --fail-at-end}} only builds the modules that do not depend on the module with 
> a failed test.
> The problem is that fork crashes like this one are written to the surefire 
> reports, so Jenkins ignores them:
> {noformat}
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> Unable to load category: stress
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:665)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
>   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
>   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356){noformat}



--
This message was sent by Atlassian

[jira] [Updated] (MSHARED-660) Upgrade to asm 6.0 for JDK9

2017-10-02 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MSHARED-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MSHARED-660:

Description: We need to upgrade the org.ow2.asm:asm dependency to 6.0 to 
support more JDK 9 in maven-dependency-plugin.

> Upgrade to asm 6.0 for JDK9
> ---
>
> Key: MSHARED-660
> URL: https://issues.apache.org/jira/browse/MSHARED-660
> Project: Maven Shared Components
>  Issue Type: Dependency upgrade
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.7
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-dependency-analyzer-1.8
>
>
> We need to upgrade the org.ow2.asm:asm dependency to 6.0 to support more JDK 
> 9 in maven-dependency-plugin.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MSHARED-660) Upgrade to asm 6.0 for JDK9

2017-10-02 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MSHARED-660:
---

 Summary: Upgrade to asm 6.0 for JDK9
 Key: MSHARED-660
 URL: https://issues.apache.org/jira/browse/MSHARED-660
 Project: Maven Shared Components
  Issue Type: Dependency upgrade
  Components: maven-dependency-analyzer
Affects Versions: maven-dependency-analyzer-1.7
Reporter: Karl Heinz Marbaise
Priority: Critical
 Fix For: maven-dependency-analyzer-1.8






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed

2017-10-02 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188044#comment-16188044
 ] 

Karl Heinz Marbaise commented on MDEP-559:
--

Hi Mark, can you first check to use  the newer version of ASM 6.0 like this:
{code:xml}
  
maven-dependency-plugin
3.0.0

  
config-dependency

  analyze

  


  
org.ow2.asm
asm
6.0
  

  
{code} 
to check if this fixes the problem. If so I can start to make changes to the 
shared component and go further.

> Java 9 bytecode cannot be parsed
> 
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9 
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @ 
> lmdbjava ---
> [DEBUG] Configuring mojo 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from 
> plugin realm 
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0, 
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo 
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with 
> basic configurator -->
> [DEBUG]   (f) analyzer = default
> [DEBUG]   (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG]   (f) failOnWarning = true
> [DEBUG]   (f) ignoreNonCompile = false
> [DEBUG]   (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG]   (f) outputXML = false
> [DEBUG]   (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @ 
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG]   (f) scriptableFlag = $$%%%
> [DEBUG]   (f) scriptableOutput = false
> [DEBUG]   (f) skip = false
> [DEBUG]   (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64, 
> org.lmdbjava:lmdbjava-native-windows-x86_64, 
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG]   (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 
> (config-dependency) on project lmdbjava: Execution config-dependency of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed. 
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 
> (config-dependency) on project lmdbjava: Execution config-dependency of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>   at 
>

[jira] [Created] (SUREFIRE-1427) Surefire-plugin throws NoClassDefFoundError with static initialiser

2017-10-02 Thread Martin Gainty (JIRA)

Martin Gainty created SUREFIRE-1427:
---

 Summary: Surefire-plugin throws NoClassDefFoundError with static 
initialiser
 Key: SUREFIRE-1427
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1427
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.20
 Environment: jdk 1.8
maven 3.3.3
Reporter: Martin Gainty
Priority: Minor


when maven-surefire-plugin encounters static initialiser such as
public class AxisDescription {
org.apache.axiom.om.OMFactory omFactory = 
org.apache.axiom.om.OMAbstractFactory.getOMFactory();
//surefire throws NoClassDefFoundError on OMAbstractFactory ?!?!?

//but if i remove static initialiser to wait until runtime to load 
OMAbstractFactory it loads ok

org.apache.axis2.description.AxisDescription:
  public void setDocumentation(String documentation) {
org.apache.axiom.om.OMFactory omFactory = 
org.apache.axiom.om.OMAbstractFactory.getOMFactory();
if (!"".equals(documentation)) {
this.documentation = omFactory.createOMText(documentation);
}
}

why does surefire not find classes referenced by static initialiser?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed

2017-10-02 Thread Mark Raynsford (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188000#comment-16188000
 ] 

Mark Raynsford commented on MDEP-559:
-

ASM 6.0 is out now. Any chance that this could fix the problem?

I'm currently blocked on converting a few projects to Java 9 because they use 
the dependency plugin's analyze step in the build.

> Java 9 bytecode cannot be parsed
> 
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9 
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @ 
> lmdbjava ---
> [DEBUG] Configuring mojo 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from 
> plugin realm 
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0, 
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo 
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with 
> basic configurator -->
> [DEBUG]   (f) analyzer = default
> [DEBUG]   (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG]   (f) failOnWarning = true
> [DEBUG]   (f) ignoreNonCompile = false
> [DEBUG]   (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG]   (f) outputXML = false
> [DEBUG]   (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @ 
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG]   (f) scriptableFlag = $$%%%
> [DEBUG]   (f) scriptableOutput = false
> [DEBUG]   (f) skip = false
> [DEBUG]   (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64, 
> org.lmdbjava:lmdbjava-native-windows-x86_64, 
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG]   (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 
> (config-dependency) on project lmdbjava: Execution config-dependency of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed. 
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 
> (config-dependency) on project lmdbjava: Execution config-dependency of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

[jira] [Commented] (MNG-5600) Dependency management import should support exclusions.

2017-10-02 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187884#comment-16187884
 ] 

ASF GitHub Bot commented on MNG-5600:
-

GitHub user jtnord opened a pull request:

https://github.com/apache/maven/pull/133

[MNG-5600] Dependency management import should support exclusions.


https://github.com/ChristianSchulte/maven/commit/679a34b86e3d69b7a832481c7f21e5eab367cd11
 cherry picked into master

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jtnord/maven MNG-5600

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/133.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #133


commit 4130977e349c6abed929e463473cbd703f13f047
Author: Christian Schulte 
Date:   2016-06-19T14:32:25Z

[MNG-5600] Dependency management import should support exclusions.




> Dependency management import should support exclusions.
> ---
>
> Key: MNG-5600
> URL: https://issues.apache.org/jira/browse/MNG-5600
> Project: Maven
>  Issue Type: Improvement
>  Components: Dependencies
>Reporter: Radai Rosenblatt
> Fix For: 3.5.x-candidate
>
>
> suppose i have a multi-module project that uses spring, and so have this in 
> dependency-managements in a parent pom:
> {code:xml}
> 
>   org.springframework
>   spring-framework-bom
>   ${org.springframework.version}
>   pom
>   import   
> 
> {code}
> spring artifacts (or at least a lot of them) have a dependency on 
> commons-logging. right now, if i want to exclude commons-logging i have to 
> add an exclusion to every spring dependency in every module of my project, 
> which is actually more XML overall than giving up on using the bom dependency 
> altogether and listing all spring dependencies with excludes once in the 
> parent dependency management.
> I'd like to be able to do this:
> {code:xml}
> 
>   org.springframework
>   spring-framework-bom
>   ${org.springframework.version}
>   pom
>   import
>   
>   
>   commons-logging
>   commons-logging
>   
>   
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-5600) Dependency management import should support exclusions.

2017-10-02 Thread James Nord (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187871#comment-16187871
 ] 

James Nord commented on MNG-5600:
-

Seems like the commit is 
https://github.com/ChristianSchulte/maven/commit/679a34b86e3d69b7a832481c7f21e5eab367cd11

> Dependency management import should support exclusions.
> ---
>
> Key: MNG-5600
> URL: https://issues.apache.org/jira/browse/MNG-5600
> Project: Maven
>  Issue Type: Improvement
>  Components: Dependencies
>Reporter: Radai Rosenblatt
> Fix For: 3.5.x-candidate
>
>
> suppose i have a multi-module project that uses spring, and so have this in 
> dependency-managements in a parent pom:
> {code:xml}
> 
>   org.springframework
>   spring-framework-bom
>   ${org.springframework.version}
>   pom
>   import   
> 
> {code}
> spring artifacts (or at least a lot of them) have a dependency on 
> commons-logging. right now, if i want to exclude commons-logging i have to 
> add an exclusion to every spring dependency in every module of my project, 
> which is actually more XML overall than giving up on using the bom dependency 
> altogether and listing all spring dependencies with excludes once in the 
> parent dependency management.
> I'd like to be able to do this:
> {code:xml}
> 
>   org.springframework
>   spring-framework-bom
>   ${org.springframework.version}
>   pom
>   import
>   
>   
>   commons-logging
>   commons-logging
>   
>   
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MINVOKER-224) Unable to set cloneProjectsTo to null

2017-10-02 Thread Stephane Nicoll (JIRA)


 [ 
https://issues.apache.org/jira/browse/MINVOKER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephane Nicoll reassigned MINVOKER-224:


 Assignee: Robert Scholte
Affects Version/s: 3.0.1
Fix Version/s: 3.0.2

> Unable to set cloneProjectsTo to null
> -
>
> Key: MINVOKER-224
> URL: https://issues.apache.org/jira/browse/MINVOKER-224
> Project: Maven Invoker Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Phillip Webb
>Assignee: Robert Scholte
> Fix For: 3.0.2
>
>
> [MINVOKER-219|https://issues.apache.org/jira/browse/MINVOKER-219] changed the 
> default value of {{cloneProjectsTo}} to {{target/its}}. This change 
> unfortunately now makes it impossible to have a {{null}} value, meaning that 
> in-place invocation is no longer supported. From the Javadoc:
> {quote}Directory to which projects should be cloned prior to execution. If 
> set to null, each integration test will be run in the directory in which the 
> corresponding IT POM was found. In this case, you most likely want to 
> configure your SCM to ignore target and build.log in the test's base 
> directory.{quote}
> Is it possible to revert this change, or to provide a alternative property to 
> allow cloning to be skipped?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

[jira] [Updated] (MCHECKSTYLE-342) Support XML 1.1

[jira] [Created] (MCHECKSTYLE-342) Support XML 1.1

[jira] [Updated] (MCHECKSTYLE-342) Support XML 1.1

[jira] [Updated] (SUREFIRE-1426) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true

[jira] [Comment Edited] (SUREFIRE-1426) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true

[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed

[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

[jira] [Comment Edited] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

[jira] [Commented] (SUREFIRE-1388) NullPointerException caused by DefaultReporterFactory.printTestFailures(DefaultReporterFactory.java:403)

[jira] [Commented] (SUREFIRE-1426) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true

[jira] [Commented] (SUREFIRE-1427) Surefire-plugin throws NoClassDefFoundError with static initialiser

[jira] [Commented] (SUREFIRE-1426) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true

[jira] [Updated] (MSHARED-660) Upgrade to asm 6.0 for JDK9

[jira] [Created] (MSHARED-660) Upgrade to asm 6.0 for JDK9

[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed

[jira] [Created] (SUREFIRE-1427) Surefire-plugin throws NoClassDefFoundError with static initialiser

[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed

[jira] [Commented] (MNG-5600) Dependency management import should support exclusions.

[jira] [Commented] (MNG-5600) Dependency management import should support exclusions.

[jira] [Assigned] (MINVOKER-224) Unable to set cloneProjectsTo to null

22 matches

Site Navigation

Mail list logo

Footer information