Re: [VOTE] Release Maven 3.2.0
+1 On Tue, Feb 11, 2014 at 3:22 AM, Jason van Zyl ja...@takari.io wrote: +1 --- Analyzer... stagingUrl: https://repository.apache.org/content/repositories/maven-1005 groupId: org.apache.maven artifactId: apache-maven version: 3.2.0 Source ZIP url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip Source ZIP SHA1 url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip.sha1 Binary ZIP url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip Binary ZIP SHA1 url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip.sha1 Calculated SHA1 of source ZIP matches published SHA1 of source ZIP. 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Calculated SHA1 of binary ZIP matches published SHA1 of binary ZIP. ff47b35b6d715dcdb3483ab9cf62178392850c19 Git revision of release as determined from maven-core-3.2.0.jar:org/apache/maven/messages/build.properties(buildNumber): 9f109b60472979a5865e9d93b72db5c0e2c37232 Files that are present in the source distribution but not in the source revision: DEPENDENCIES On Feb 10, 2014, at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira with 33 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565 Staging repo: https://repository.apache.org/content/repositories/maven-1005/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.tar.gz https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.tar.gz Source release checksum(s): apache-maven-3.2.0-src.zip sha1: 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Staging site: http://people.apache.org/~jvanzyl/maven-3.2.0/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham
Re: [VOTE] Release Apache Maven Plugin Testing version 3.1.0
+1 On 8 February 2014 17:02, Igor Fedorenko i...@ifedorenko.com wrote: Hi, We solved 2 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=20031 There are still a couple of issues left in JIRA: https://jira.codehaus.org/browse/MPLUGINTESTING-20?jql=project%20%3D%20MPLUGINTESTING%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1003 http://repository.apache.org/content/repositories/maven-1003/org/apache/maven/plugin-testing/maven-plugin-testing/3.1.0/maven-plugin-testing-3.1.0-source-release.zip Source release checksum(s): 890593b10fe868f57fa52e37aacdaa05d8803bd4 maven-plugin-testing-3.1.0-source-release.zip Staging site: http://maven.apache.org/plugin-testing-archives/LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.0
Hello, not sure what's happening here. There seems to be a regression with the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1). What I did: - Checked out https://github.com/1and1/testlink-junit - Now running mvn320 -V -e clean verify gives the following: 12670 [ERROR] Failed to execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent (default-prepare-agent) on project tljunit-surefire: Execution default-prepare-agent of goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent failed. NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent (default-prepare-agent) on project tljunit-surefire: Execution default-prepare-agent of goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) 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:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-prepare-agent of goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:144) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: java.lang.NullPointerException at org.jacoco.maven.AbstractAgentMojo.getAgentJarFile(AbstractAgentMojo.java:151) at org.jacoco.maven.AbstractAgentMojo.executeMojo(AbstractAgentMojo.java:142) at org.jacoco.maven.AbstractJacocoMojo.execute(AbstractJacocoMojo.java:72) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) ... 20 more Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Feb 11, 2014 at 9:55 AM, Tamás Cservenák ta...@cservenak.net wrote: +1 On Tue, Feb 11, 2014 at 3:22 AM, Jason van Zyl ja...@takari.io wrote: +1 --- Analyzer... stagingUrl: https://repository.apache.org/content/repositories/maven-1005 groupId: org.apache.maven artifactId: apache-maven version: 3.2.0 Source ZIP url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip Source ZIP SHA1 url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip.sha1 Binary ZIP url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip Binary ZIP SHA1 url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip.sha1 Calculated SHA1 of source ZIP matches published SHA1 of source ZIP. 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Calculated SHA1 of binary ZIP matches published SHA1 of binary ZIP. ff47b35b6d715dcdb3483ab9cf62178392850c19 Git revision of release as determined from maven-core-3.2.0.jar:org/apache/maven/messages/build.properties(buildNumber): 9f109b60472979a5865e9d93b72db5c0e2c37232 Files that are present in the source distribution but not in the source revision: DEPENDENCIES On Feb 10, 2014, at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira
Re: [VOTE] Release Maven 3.2.0
I will take a look, I found another issue of my own too. Boo. On Feb 11, 2014, at 10:42 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, not sure what's happening here. There seems to be a regression with the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1). What I did: - Checked out https://github.com/1and1/testlink-junit - Now running mvn320 -V -e clean verify gives the following: 12670 [ERROR] Failed to execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent (default-prepare-agent) on project tljunit-surefire: Execution default-prepare-agent of goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent failed. NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent (default-prepare-agent) on project tljunit-surefire: Execution default-prepare-agent of goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) 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:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-prepare-agent of goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:144) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: java.lang.NullPointerException at org.jacoco.maven.AbstractAgentMojo.getAgentJarFile(AbstractAgentMojo.java:151) at org.jacoco.maven.AbstractAgentMojo.executeMojo(AbstractAgentMojo.java:142) at org.jacoco.maven.AbstractJacocoMojo.execute(AbstractJacocoMojo.java:72) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) ... 20 more Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Feb 11, 2014 at 9:55 AM, Tamás Cservenák ta...@cservenak.net wrote: +1 On Tue, Feb 11, 2014 at 3:22 AM, Jason van Zyl ja...@takari.io wrote: +1 --- Analyzer... stagingUrl: https://repository.apache.org/content/repositories/maven-1005 groupId: org.apache.maven artifactId: apache-maven version: 3.2.0 Source ZIP url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip Source ZIP SHA1 url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip.sha1 Binary ZIP url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip Binary ZIP SHA1 url exists. https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip.sha1 Calculated SHA1 of source ZIP matches published SHA1 of source ZIP. 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Calculated SHA1 of binary ZIP matches published SHA1 of binary ZIP. ff47b35b6d715dcdb3483ab9cf62178392850c19 Git revision of release as determined from maven-core-3.2.0.jar:org/apache/maven/messages/build.properties(buildNumber):
Re: [VOTE] Release Maven 3.2.0
Regression from Apache Maven 3.1.1, seen via: bash$ mvn -e -Dmaven.test.skip=true -DskipTests=true -T 2.0C clean install $@ [ERROR] Error executing Maven. java.lang.NumberFormatException: For input string: 2.0 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.valueOf(Integer.java:582) at org.apache.maven.cli.MavenCli.populateRequest(MavenCli.java:1092) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:210) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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) I'd say this would be a blocker, we use --threads * core multiplier support on a variety of platforms for automatic scaling. On Mon, Feb 10, 2014 at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Time to release Maven 3.2.0! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.0
Yup, I consider it a blocker. I'll fix that. On Feb 11, 2014, at 12:57 PM, jieryn jie...@gmail.com wrote: Regression from Apache Maven 3.1.1, seen via: bash$ mvn -e -Dmaven.test.skip=true -DskipTests=true -T 2.0C clean install $@ [ERROR] Error executing Maven. java.lang.NumberFormatException: For input string: 2.0 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.valueOf(Integer.java:582) at org.apache.maven.cli.MavenCli.populateRequest(MavenCli.java:1092) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:210) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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) I'd say this would be a blocker, we use --threads * core multiplier support on a variety of platforms for automatic scaling. On Mon, Feb 10, 2014 at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Time to release Maven 3.2.0! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We all have problems. How we deal with them is a measure of our worth. -- Unknown
Re: [VOTE] Release Maven 3.2.0
Are you formally cancelling this vote, or waiting for more to show in the wash? On Tuesday, 11 February 2014, Jason van Zyl ja...@takari.io wrote: Yup, I consider it a blocker. I'll fix that. On Feb 11, 2014, at 12:57 PM, jieryn jie...@gmail.com javascript:; wrote: Regression from Apache Maven 3.1.1, seen via: bash$ mvn -e -Dmaven.test.skip=true -DskipTests=true -T 2.0C clean install $@ [ERROR] Error executing Maven. java.lang.NumberFormatException: For input string: 2.0 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.valueOf(Integer.java:582) at org.apache.maven.cli.MavenCli.populateRequest(MavenCli.java:1092) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:210) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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) I'd say this would be a blocker, we use --threads * core multiplier support on a variety of platforms for automatic scaling. On Mon, Feb 10, 2014 at 9:18 PM, Jason van Zyl ja...@takari.iojavascript:; wrote: Time to release Maven 3.2.0! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.orgjavascript:; Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We all have problems. How we deal with them is a measure of our worth. -- Unknown -- Sent from my phone
Re: [VOTE] Release Apache Maven Plugin Testing version 3.1.0
Can I get another PMC vote please? -- Regards, Igor On 2/8/2014, 1:02, Igor Fedorenko wrote: Hi, We solved 2 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=20031 There are still a couple of issues left in JIRA: https://jira.codehaus.org/browse/MPLUGINTESTING-20?jql=project%20%3D%20MPLUGINTESTING%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1003 http://repository.apache.org/content/repositories/maven-1003/org/apache/maven/plugin-testing/maven-plugin-testing/3.1.0/maven-plugin-testing-3.1.0-source-release.zip Source release checksum(s): 890593b10fe868f57fa52e37aacdaa05d8803bd4 maven-plugin-testing-3.1.0-source-release.zip Staging site: http://maven.apache.org/plugin-testing-archives/LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Plugin Testing version 3.1.0
On Tue, Feb 11, 2014 at 2:48 PM, Igor Fedorenko i...@ifedorenko.com wrote: 890593b10fe868f57fa52e37aacdaa05d8803bd4 +1 (binding). It would be helpful if the template said that the checksum was sha1 :-) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Plugin Testing version 3.1.0
+1 Regards, Hervé Le samedi 8 février 2014 01:02:24 Igor Fedorenko a écrit : Hi, We solved 2 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=20 031 There are still a couple of issues left in JIRA: https://jira.codehaus.org/browse/MPLUGINTESTING-20?jql=project%20%3D%20MPLUG INTESTING%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DE SC Staging repo: https://repository.apache.org/content/repositories/maven-1003 http://repository.apache.org/content/repositories/maven-1003/org/apache/mave n/plugin-testing/maven-plugin-testing/3.1.0/maven-plugin-testing-3.1.0-sourc e-release.zip Source release checksum(s): 890593b10fe868f57fa52e37aacdaa05d8803bd4 maven-plugin-testing-3.1.0-source-release.zip Staging site: http://maven.apache.org/plugin-testing-archives/LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.0
Sorry, stepped away for a bit. I'm going to cancel the vote. On Feb 11, 2014, at 1:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Are you formally cancelling this vote, or waiting for more to show in the wash? On Tuesday, 11 February 2014, Jason van Zyl ja...@takari.io wrote: Yup, I consider it a blocker. I'll fix that. On Feb 11, 2014, at 12:57 PM, jieryn jie...@gmail.com javascript:; wrote: Regression from Apache Maven 3.1.1, seen via: bash$ mvn -e -Dmaven.test.skip=true -DskipTests=true -T 2.0C clean install $@ [ERROR] Error executing Maven. java.lang.NumberFormatException: For input string: 2.0 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.valueOf(Integer.java:582) at org.apache.maven.cli.MavenCli.populateRequest(MavenCli.java:1092) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:210) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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) I'd say this would be a blocker, we use --threads * core multiplier support on a variety of platforms for automatic scaling. On Mon, Feb 10, 2014 at 9:18 PM, Jason van Zyl ja...@takari.iojavascript:; wrote: Time to release Maven 3.2.0! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.orgjavascript:; Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We all have problems. How we deal with them is a measure of our worth. -- Unknown -- Sent from my phone Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - I never make the mistake of arguing with people for whose opinions I have no respect. -- Edward Gibbon
[VOTE][CANCELLED] Release Maven 3.2.0
Couple issues cropped up so I'm canceling the vote. On Feb 10, 2014, at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira with 33 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565 Staging repo: https://repository.apache.org/content/repositories/maven-1005/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.tar.gz https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.tar.gz Source release checksum(s): apache-maven-3.2.0-src.zip sha1: 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Staging site: http://people.apache.org/~jvanzyl/maven-3.2.0/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - A language that doesn’t affect the way you think about programming is not worth knowing. -- Alan Perlis
Re: [VOTE] Release Maven 3.2.0
I know its already cancelled but -1 from me. I'm seeing my large IT build just lock up and hang solid resolving dependencies. Looks to be an issue in org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter Thread dump: https://gist.github.com/talios/f4434d5c65e882a7e9d2 Subsequent calls to jstack show more depths of org.eclipse.aether.graph.DefaultDependencyNode.accept in the stack. And boy - I think this is the first time I've heard the fan on my new MacBook Pro!! Mark On 11 Feb 2014, at 15:18, Jason van Zyl wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira with 33 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565 Staging repo: https://repository.apache.org/content/repositories/maven-1005/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.tar.gz https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.tar.gz Source release checksum(s): apache-maven-3.2.0-src.zip sha1: 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Staging site: http://people.apache.org/~jvanzyl/maven-3.2.0/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.0
Hello,
I probably found the culprit for my issue
https://jira.codehaus.org/browse/MNG-5552:
- This introduces the option to use a classifier when looking up stuff
from the ${plugin.artifactMap}
- Now the jacoco-maven-plugin uses an agent
(GAVC=org.jacoco:org.jacoco.agent:VERSION:runtime) which has a
classifier runtime.
- With Maven 3.2.0 the agent could be looked up (artifactMap.get)
with org.jacoco:org.jacoco.agent, the key in the map was GA.
- With Maven 3.2.0 the key is now GAC (org.jacoco:org.jacoco.agent:runtime)
- So now you are forced to give the classifier as well for the lookup,
when doing this it will break backwards compatibility.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Feb 11, 2014 at 4:42 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
not sure what's happening here. There seems to be a regression with
the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1).
What I did:
- Checked out https://github.com/1and1/testlink-junit
- Now running mvn320 -V -e clean verify gives the following:
12670 [ERROR] Failed to execute goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed. NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:108)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:144)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.NullPointerException
at
org.jacoco.maven.AbstractAgentMojo.getAgentJarFile(AbstractAgentMojo.java:151)
at org.jacoco.maven.AbstractAgentMojo.executeMojo(AbstractAgentMojo.java:142)
at org.jacoco.maven.AbstractJacocoMojo.execute(AbstractJacocoMojo.java:72)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
... 20 more
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Feb 11, 2014 at 9:55 AM, Tamás Cservenák ta...@cservenak.net wrote:
+1
On Tue, Feb 11, 2014 at 3:22 AM, Jason van Zyl ja...@takari.io wrote:
+1
---
Analyzer...
stagingUrl: https://repository.apache.org/content/repositories/maven-1005
groupId: org.apache.maven
artifactId: apache-maven
version: 3.2.0
Source ZIP url exists.
https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip
Source ZIP SHA1 url exists.
Re: [VOTE][CANCELLED] Release Maven 3.2.0
Noticed this non blocking issue when using activemq plugin to start an activemq instance: [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 17.840s [INFO] Finished at: Wed Feb 12 09:12:23 EST 2014 [INFO] Final Memory: 33M/733M [INFO] [INFO] Apache ActiveMQ 5.9.0 (localhost, ID:mb-olamy.local-49682-1392156741632-0:1) is shutting down [INFO] Connector tcp://localhost:49681 stopped Exception in thread ActiveMQ ShutdownHook java.lang.NoClassDefFoundError: org/apache/activemq/transport/vm/VMTransportFactory at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:733) at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2348) at org.apache.activemq.broker.BrokerService$6.run(BrokerService.java:2315) Caused by: java.lang.ClassNotFoundException: org.apache.activemq.transport.vm.VMTransportFactory at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) ... 3 more Not blocker as it work as expected but just a bit annoying On 12 February 2014 07:37, Jason van Zyl ja...@takari.io wrote: Couple issues cropped up so I'm canceling the vote. On Feb 10, 2014, at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira with 33 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565 Staging repo: https://repository.apache.org/content/repositories/maven-1005/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.tar.gz https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.tar.gz Source release checksum(s): apache-maven-3.2.0-src.zip sha1: 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Staging site: http://people.apache.org/~jvanzyl/maven-3.2.0/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - A language that doesn't affect the way you think about programming is not worth knowing. -- Alan Perlis -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.0
This is kinda tricky. We have three cases to consider
1. Plugin depends on main artifact only. For such dependency both 3.1.1
and 3.2.0 use G:A key, so there is no problem there
2. Plugin depends on main and classified artifacts of the same GA. In
this case 3.1.1 picked the last artifact and used it with G:A key,
while 3.2.0 uses G:A for the main artifact and G:A:C for classified
artifacts.
3. Plugin depends on classified artifact only. In this case 3.1.1 uses
G:A key and 3.2.0 uses G:A:C
And I really need to support case #2 ;-)
The only 100% backwards compatible solution seems to keep the original
MavenProject#pluginArtifactMap and MavenProject#artifactMap as is, but
deprecate them and introduce new behaviour as new #pluginArtifactMapC
and #artifactMap members.
Does anyone see other options?
--
Regards,
Igor
On 2/11/2014, 16:39, Mirko Friedenhagen wrote:
Hello,
I probably found the culprit for my issue
https://jira.codehaus.org/browse/MNG-5552:
- This introduces the option to use a classifier when looking up stuff
from the ${plugin.artifactMap}
- Now the jacoco-maven-plugin uses an agent
(GAVC=org.jacoco:org.jacoco.agent:VERSION:runtime) which has a
classifier runtime.
- With Maven 3.2.0 the agent could be looked up (artifactMap.get)
with org.jacoco:org.jacoco.agent, the key in the map was GA.
- With Maven 3.2.0 the key is now GAC (org.jacoco:org.jacoco.agent:runtime)
- So now you are forced to give the classifier as well for the lookup,
when doing this it will break backwards compatibility.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Feb 11, 2014 at 4:42 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
not sure what's happening here. There seems to be a regression with
the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1).
What I did:
- Checked out https://github.com/1and1/testlink-junit
- Now running mvn320 -V -e clean verify gives the following:
12670 [ERROR] Failed to execute goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed. NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:108)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:144)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.NullPointerException
at
org.jacoco.maven.AbstractAgentMojo.getAgentJarFile(AbstractAgentMojo.java:151)
at org.jacoco.maven.AbstractAgentMojo.executeMojo(AbstractAgentMojo.java:142)
at org.jacoco.maven.AbstractJacocoMojo.execute(AbstractJacocoMojo.java:72)
at
Re: [VOTE] Release Maven 3.2.0
I wish not to rehash any previous debate (if one occurred), but it would be
nice to abandon 3.2.0 and start 3.2.1 for the blocker fixes. I think it
makes issue tracking and voting easier than re-spinning the same version
number. What are your thoughts?
On Tue, Feb 11, 2014 at 4:40 PM, Igor Fedorenko i...@ifedorenko.com wrote:
This is kinda tricky. We have three cases to consider
1. Plugin depends on main artifact only. For such dependency both 3.1.1
and 3.2.0 use G:A key, so there is no problem there
2. Plugin depends on main and classified artifacts of the same GA. In
this case 3.1.1 picked the last artifact and used it with G:A key,
while 3.2.0 uses G:A for the main artifact and G:A:C for classified
artifacts.
3. Plugin depends on classified artifact only. In this case 3.1.1 uses
G:A key and 3.2.0 uses G:A:C
And I really need to support case #2 ;-)
The only 100% backwards compatible solution seems to keep the original
MavenProject#pluginArtifactMap and MavenProject#artifactMap as is, but
deprecate them and introduce new behaviour as new #pluginArtifactMapC
and #artifactMap members.
Does anyone see other options?
--
Regards,
Igor
On 2/11/2014, 16:39, Mirko Friedenhagen wrote:
Hello,
I probably found the culprit for my issue
https://jira.codehaus.org/browse/MNG-5552:
- This introduces the option to use a classifier when looking up stuff
from the ${plugin.artifactMap}
- Now the jacoco-maven-plugin uses an agent
(GAVC=org.jacoco:org.jacoco.agent:VERSION:runtime) which has a
classifier runtime.
- With Maven 3.2.0 the agent could be looked up (artifactMap.get)
with org.jacoco:org.jacoco.agent, the key in the map was GA.
- With Maven 3.2.0 the key is now GAC (org.jacoco:org.jacoco.agent:
runtime)
- So now you are forced to give the classifier as well for the lookup,
when doing this it will break backwards compatibility.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Feb 11, 2014 at 4:42 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
not sure what's happening here. There seems to be a regression with
the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1).
What I did:
- Checked out https://github.com/1and1/testlink-junit
- Now running mvn320 -V -e clean verify gives the following:
12670 [ERROR] Failed to execute goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed. NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:
prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:224)
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:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.
SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.
execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
DefaultBuildPluginManager.java:144)
at
Re: [VOTE] Release Maven 3.2.0
Yes, I agree 3.2.1 makes sense. Still need to decide what to do with
artifact maps, though :-)
--
Regards,
Igor
On 2/11/2014, 17:48, Paul Benedict wrote:
I wish not to rehash any previous debate (if one occurred), but it would be
nice to abandon 3.2.0 and start 3.2.1 for the blocker fixes. I think it
makes issue tracking and voting easier than re-spinning the same version
number. What are your thoughts?
On Tue, Feb 11, 2014 at 4:40 PM, Igor Fedorenko i...@ifedorenko.com wrote:
This is kinda tricky. We have three cases to consider
1. Plugin depends on main artifact only. For such dependency both 3.1.1
and 3.2.0 use G:A key, so there is no problem there
2. Plugin depends on main and classified artifacts of the same GA. In
this case 3.1.1 picked the last artifact and used it with G:A key,
while 3.2.0 uses G:A for the main artifact and G:A:C for classified
artifacts.
3. Plugin depends on classified artifact only. In this case 3.1.1 uses
G:A key and 3.2.0 uses G:A:C
And I really need to support case #2 ;-)
The only 100% backwards compatible solution seems to keep the original
MavenProject#pluginArtifactMap and MavenProject#artifactMap as is, but
deprecate them and introduce new behaviour as new #pluginArtifactMapC
and #artifactMap members.
Does anyone see other options?
--
Regards,
Igor
On 2/11/2014, 16:39, Mirko Friedenhagen wrote:
Hello,
I probably found the culprit for my issue
https://jira.codehaus.org/browse/MNG-5552:
- This introduces the option to use a classifier when looking up stuff
from the ${plugin.artifactMap}
- Now the jacoco-maven-plugin uses an agent
(GAVC=org.jacoco:org.jacoco.agent:VERSION:runtime) which has a
classifier runtime.
- With Maven 3.2.0 the agent could be looked up (artifactMap.get)
with org.jacoco:org.jacoco.agent, the key in the map was GA.
- With Maven 3.2.0 the key is now GAC (org.jacoco:org.jacoco.agent:
runtime)
- So now you are forced to give the classifier as well for the lookup,
when doing this it will break backwards compatibility.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Feb 11, 2014 at 4:42 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
not sure what's happening here. There seems to be a regression with
the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1).
What I did:
- Checked out https://github.com/1and1/testlink-junit
- Now running mvn320 -V -e clean verify gives the following:
12670 [ERROR] Failed to execute goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed. NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:
prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:224)
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:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.
SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.
execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at
Re: [VOTE] Release Maven 3.2.0
Good luck... any time I have tried to win that battle I have been voted
down!
On 11 February 2014 22:48, Paul Benedict pbened...@apache.org wrote:
I wish not to rehash any previous debate (if one occurred), but it would be
nice to abandon 3.2.0 and start 3.2.1 for the blocker fixes. I think it
makes issue tracking and voting easier than re-spinning the same version
number. What are your thoughts?
On Tue, Feb 11, 2014 at 4:40 PM, Igor Fedorenko i...@ifedorenko.com
wrote:
This is kinda tricky. We have three cases to consider
1. Plugin depends on main artifact only. For such dependency both 3.1.1
and 3.2.0 use G:A key, so there is no problem there
2. Plugin depends on main and classified artifacts of the same GA. In
this case 3.1.1 picked the last artifact and used it with G:A key,
while 3.2.0 uses G:A for the main artifact and G:A:C for classified
artifacts.
3. Plugin depends on classified artifact only. In this case 3.1.1 uses
G:A key and 3.2.0 uses G:A:C
And I really need to support case #2 ;-)
The only 100% backwards compatible solution seems to keep the original
MavenProject#pluginArtifactMap and MavenProject#artifactMap as is, but
deprecate them and introduce new behaviour as new #pluginArtifactMapC
and #artifactMap members.
Does anyone see other options?
--
Regards,
Igor
On 2/11/2014, 16:39, Mirko Friedenhagen wrote:
Hello,
I probably found the culprit for my issue
https://jira.codehaus.org/browse/MNG-5552:
- This introduces the option to use a classifier when looking up stuff
from the ${plugin.artifactMap}
- Now the jacoco-maven-plugin uses an agent
(GAVC=org.jacoco:org.jacoco.agent:VERSION:runtime) which has a
classifier runtime.
- With Maven 3.2.0 the agent could be looked up (artifactMap.get)
with org.jacoco:org.jacoco.agent, the key in the map was GA.
- With Maven 3.2.0 the key is now GAC (org.jacoco:org.jacoco.agent:
runtime)
- So now you are forced to give the classifier as well for the lookup,
when doing this it will break backwards compatibility.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Feb 11, 2014 at 4:42 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
not sure what's happening here. There seems to be a regression with
the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1).
What I did:
- Checked out https://github.com/1and1/testlink-junit
- Now running mvn320 -V -e clean verify gives the following:
12670 [ERROR] Failed to execute goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed. NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:
prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:224)
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:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.
SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.
execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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)
Caused by:
Re: [VOTE][CANCELLED] Release Maven 3.2.0
On 11 February 2014 22:15, Olivier Lamy ol...@apache.org wrote: Noticed this non blocking issue when using activemq plugin to start an activemq instance: [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 17.840s [INFO] Finished at: Wed Feb 12 09:12:23 EST 2014 [INFO] Final Memory: 33M/733M [INFO] [INFO] Apache ActiveMQ 5.9.0 (localhost, ID:mb-olamy.local-49682-1392156741632-0:1) is shutting down [INFO] Connector tcp://localhost:49681 stopped Exception in thread ActiveMQ ShutdownHook java.lang.NoClassDefFoundError: org/apache/activemq/transport/vm/VMTransportFactory I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. This happens after the Maven build is finished, but before JVM shutdown hooks run. Any plugin that registers a JVM shutdown hook which tries to load classes/resources from the original plugin realm will throw a NCDFE - you'll probably see similar issues if a plugin forks threads that are still running after the plugin/container realm has been disposed and subsequently try to load classes. ( note that the same error will likely occur with Maven 3.1.1 since it uses the same version of Classworlds ) at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:733) at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2348) at org.apache.activemq.broker.BrokerService$6.run(BrokerService.java:2315) Caused by: java.lang.ClassNotFoundException: org.apache.activemq.transport.vm.VMTransportFactory at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) ... 3 more Not blocker as it work as expected but just a bit annoying On 12 February 2014 07:37, Jason van Zyl ja...@takari.io wrote: Couple issues cropped up so I'm canceling the vote. On Feb 10, 2014, at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira with 33 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565 Staging repo: https://repository.apache.org/content/repositories/maven-1005/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.tar.gz https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.tar.gz Source release checksum(s): apache-maven-3.2.0-src.zip sha1: 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Staging site: http://people.apache.org/~jvanzyl/maven-3.2.0/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - A language that doesn't affect the way you think about programming is not worth knowing. -- Alan Perlis -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Cheers, Stuart
Re: [VOTE][CANCELLED] Release Maven 3.2.0
Thanks Stuart for this confirmation, I am seeing this exact issue happen on both 3.1.x and 3.2. My build uses truezip-maven-plugin [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 19.347s [INFO] Finished at: Tue Feb 11 15:24:26 PST 2014 [INFO] Final Memory: 33M/698M [INFO] java.lang.NoClassDefFoundError: de/schlichtherle/truezip/fs/FsSyncOptions at de.schlichtherle.truezip.fs.FsSyncShutdownHook$Hook.run(FsSyncShutdownHook.java:93) Caused by: java.lang.ClassNotFoundException: de.schlichtherle.truezip.fs.FsSyncOptions at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.ja va:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java: 259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) ... 1 more On Tue, Feb 11, 2014 at 3:20 PM, Stuart McCulloch mccu...@gmail.com wrote: On 11 February 2014 22:15, Olivier Lamy ol...@apache.org wrote: Noticed this non blocking issue when using activemq plugin to start an activemq instance: [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 17.840s [INFO] Finished at: Wed Feb 12 09:12:23 EST 2014 [INFO] Final Memory: 33M/733M [INFO] [INFO] Apache ActiveMQ 5.9.0 (localhost, ID:mb-olamy.local-49682-1392156741632-0:1) is shutting down [INFO] Connector tcp://localhost:49681 stopped Exception in thread ActiveMQ ShutdownHook java.lang.NoClassDefFoundError: org/apache/activemq/transport/vm/VMTransportFactory I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. This happens after the Maven build is finished, but before JVM shutdown hooks run. Any plugin that registers a JVM shutdown hook which tries to load classes/resources from the original plugin realm will throw a NCDFE - you'll probably see similar issues if a plugin forks threads that are still running after the plugin/container realm has been disposed and subsequently try to load classes. ( note that the same error will likely occur with Maven 3.1.1 since it uses the same version of Classworlds ) at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:733) at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2348) at org.apache.activemq.broker.BrokerService$6.run(BrokerService.java:2315) Caused by: java.lang.ClassNotFoundException: org.apache.activemq.transport.vm.VMTransportFactory at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) ... 3 more Not blocker as it work as expected but just a bit annoying On 12 February 2014 07:37, Jason van Zyl ja...@takari.io wrote: Couple issues cropped up so I'm canceling the vote. On Feb 10, 2014, at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira with 33 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565 Staging repo: https://repository.apache.org/content/repositories/maven-1005/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.tar.gz https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.tar.gz Source release checksum(s): apache-maven-3.2.0-src.zip sha1: 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Staging site: http://people.apache.org/~jvanzyl/maven-3.2.0/
Re: [VOTE][CANCELLED] Release Maven 3.2.0
On 11 February 2014 23:26, Dan Tran dant...@gmail.com wrote: Thanks Stuart for this confirmation, I am seeing this exact issue happen on both 3.1.x and 3.2. My build uses truezip-maven-plugin Yep, TrueZip will leave a JVM shutdown hook registered unless you explicitly unmount the virtual file system after you're done with it - in most cases this is just an oversight and unmounting will also help conserve resources, see example in https://github.com/klieber/phantomjs-maven-plugin/pull/19/files [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 19.347s [INFO] Finished at: Tue Feb 11 15:24:26 PST 2014 [INFO] Final Memory: 33M/698M [INFO] java.lang.NoClassDefFoundError: de/schlichtherle/truezip/fs/FsSyncOptions at de.schlichtherle.truezip.fs.FsSyncShutdownHook$Hook.run(FsSyncShutdownHook.java:93) Caused by: java.lang.ClassNotFoundException: de.schlichtherle.truezip.fs.FsSyncOptions at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.ja va:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java: 259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) ... 1 more On Tue, Feb 11, 2014 at 3:20 PM, Stuart McCulloch mccu...@gmail.com wrote: On 11 February 2014 22:15, Olivier Lamy ol...@apache.org wrote: Noticed this non blocking issue when using activemq plugin to start an activemq instance: [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 17.840s [INFO] Finished at: Wed Feb 12 09:12:23 EST 2014 [INFO] Final Memory: 33M/733M [INFO] [INFO] Apache ActiveMQ 5.9.0 (localhost, ID:mb-olamy.local-49682-1392156741632-0:1) is shutting down [INFO] Connector tcp://localhost:49681 stopped Exception in thread ActiveMQ ShutdownHook java.lang.NoClassDefFoundError: org/apache/activemq/transport/vm/VMTransportFactory I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. This happens after the Maven build is finished, but before JVM shutdown hooks run. Any plugin that registers a JVM shutdown hook which tries to load classes/resources from the original plugin realm will throw a NCDFE - you'll probably see similar issues if a plugin forks threads that are still running after the plugin/container realm has been disposed and subsequently try to load classes. ( note that the same error will likely occur with Maven 3.1.1 since it uses the same version of Classworlds ) at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:733) at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2348) at org.apache.activemq.broker.BrokerService$6.run(BrokerService.java:2315) Caused by: java.lang.ClassNotFoundException: org.apache.activemq.transport.vm.VMTransportFactory at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) ... 3 more Not blocker as it work as expected but just a bit annoying On 12 February 2014 07:37, Jason van Zyl ja...@takari.io wrote: Couple issues cropped up so I'm canceling the vote. On Feb 10, 2014, at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira with 33 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565 Staging repo: https://repository.apache.org/content/repositories/maven-1005/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip
Re: [VOTE][CANCELLED] Release Maven 3.2.0
On Tue, Feb 11, 2014 at 3:20 PM, Stuart McCulloch mccu...@gmail.com wrote: I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. Just as an aside, this sent me scrambling to my Javadocs; I see no such close() method on ClassLoader in any version of Java? (See for example http://download.java.net/jdk8/docs/api/java/lang/ClassLoader.html) Typo? Best, Laird -- http://about.me/lairdnelson
Re: [VOTE][CANCELLED] Release Maven 3.2.0
http://download.java.net/jdk8/docs/api/java/net/URLClassLoader.html -- Regards, Igor On 2/11/2014, 18:38, Laird Nelson wrote: On Tue, Feb 11, 2014 at 3:20 PM, Stuart McCulloch mccu...@gmail.com wrote: I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. Just as an aside, this sent me scrambling to my Javadocs; I see no such close() method on ClassLoader in any version of Java? (See for example http://download.java.net/jdk8/docs/api/java/lang/ClassLoader.html) Typo? Best, Laird - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
How to skip the execution of batch file based on need in maven build
Added exec-maven-plugin pulgin in pom.xml plugins . plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId version1.2/version executions execution idrunbatchfile/id phasepackage/phase goals goalexec/goal /goals /execution /executions configuration executabletest.bat/executable /configuration /plugin /plugins When I execute the cmd 'mvn clean install' my bat file test.bat is getting executed. I wanted to execute the batch file on need basis. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-skip-the-execution-of-batch-file-based-on-need-in-maven-build-tp5783909.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
Hi Apologies for posting in a too general mailing list but I could not find a better one. I have a question about the expected behaviour of the deploy:deploy-file goal in the maven deploy plugin 2.8.1 which I am currently using to deploy one file. It surprised me that no matter what I did I kept getting more artifacts deployed that I asked for and the reason is in the org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376 where the attached artifacts are also deployed. Is this intended behaviour and if so how can I avoid this from happening? The goal name deploy-file indicates that one artifact (possible incl. pom/metadata) is to be deployed and not also a throng of other artifacts. I will be happy to provide a patch where this is aspect is removed. Thank you in advance regards Henrik Skriver Rasmussen
Re: [VOTE] Release Maven 3.2.0
It's definitely easier for me if we just move forward, even though I think it's
confusing for users. But I'm fine with it, 3.2.1 it is.
On Feb 11, 2014, at 5:48 PM, Paul Benedict pbened...@apache.org wrote:
I wish not to rehash any previous debate (if one occurred), but it would be
nice to abandon 3.2.0 and start 3.2.1 for the blocker fixes. I think it
makes issue tracking and voting easier than re-spinning the same version
number. What are your thoughts?
On Tue, Feb 11, 2014 at 4:40 PM, Igor Fedorenko i...@ifedorenko.com wrote:
This is kinda tricky. We have three cases to consider
1. Plugin depends on main artifact only. For such dependency both 3.1.1
and 3.2.0 use G:A key, so there is no problem there
2. Plugin depends on main and classified artifacts of the same GA. In
this case 3.1.1 picked the last artifact and used it with G:A key,
while 3.2.0 uses G:A for the main artifact and G:A:C for classified
artifacts.
3. Plugin depends on classified artifact only. In this case 3.1.1 uses
G:A key and 3.2.0 uses G:A:C
And I really need to support case #2 ;-)
The only 100% backwards compatible solution seems to keep the original
MavenProject#pluginArtifactMap and MavenProject#artifactMap as is, but
deprecate them and introduce new behaviour as new #pluginArtifactMapC
and #artifactMap members.
Does anyone see other options?
--
Regards,
Igor
On 2/11/2014, 16:39, Mirko Friedenhagen wrote:
Hello,
I probably found the culprit for my issue
https://jira.codehaus.org/browse/MNG-5552:
- This introduces the option to use a classifier when looking up stuff
from the ${plugin.artifactMap}
- Now the jacoco-maven-plugin uses an agent
(GAVC=org.jacoco:org.jacoco.agent:VERSION:runtime) which has a
classifier runtime.
- With Maven 3.2.0 the agent could be looked up (artifactMap.get)
with org.jacoco:org.jacoco.agent, the key in the map was GA.
- With Maven 3.2.0 the key is now GAC (org.jacoco:org.jacoco.agent:
runtime)
- So now you are forced to give the classifier as well for the lookup,
when doing this it will break backwards compatibility.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Feb 11, 2014 at 4:42 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
not sure what's happening here. There seems to be a regression with
the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1).
What I did:
- Checked out https://github.com/1and1/testlink-junit
- Now running mvn320 -V -e clean verify gives the following:
12670 [ERROR] Failed to execute goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed. NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:
prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:224)
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:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.
SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.
execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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)
Caused by:
Re: [VOTE] Release Maven 3.2.0
Hurrah! At last!
(at least until the there must be a .0 release or the world will end gang
on the PMC bash us back to 3.2.0)
On 12 February 2014 00:02, Jason van Zyl ja...@takari.io wrote:
It's definitely easier for me if we just move forward, even though I think
it's confusing for users. But I'm fine with it, 3.2.1 it is.
On Feb 11, 2014, at 5:48 PM, Paul Benedict pbened...@apache.org wrote:
I wish not to rehash any previous debate (if one occurred), but it would
be
nice to abandon 3.2.0 and start 3.2.1 for the blocker fixes. I think it
makes issue tracking and voting easier than re-spinning the same version
number. What are your thoughts?
On Tue, Feb 11, 2014 at 4:40 PM, Igor Fedorenko i...@ifedorenko.com
wrote:
This is kinda tricky. We have three cases to consider
1. Plugin depends on main artifact only. For such dependency both 3.1.1
and 3.2.0 use G:A key, so there is no problem there
2. Plugin depends on main and classified artifacts of the same GA. In
this case 3.1.1 picked the last artifact and used it with G:A key,
while 3.2.0 uses G:A for the main artifact and G:A:C for classified
artifacts.
3. Plugin depends on classified artifact only. In this case 3.1.1 uses
G:A key and 3.2.0 uses G:A:C
And I really need to support case #2 ;-)
The only 100% backwards compatible solution seems to keep the original
MavenProject#pluginArtifactMap and MavenProject#artifactMap as is, but
deprecate them and introduce new behaviour as new #pluginArtifactMapC
and #artifactMap members.
Does anyone see other options?
--
Regards,
Igor
On 2/11/2014, 16:39, Mirko Friedenhagen wrote:
Hello,
I probably found the culprit for my issue
https://jira.codehaus.org/browse/MNG-5552:
- This introduces the option to use a classifier when looking up stuff
from the ${plugin.artifactMap}
- Now the jacoco-maven-plugin uses an agent
(GAVC=org.jacoco:org.jacoco.agent:VERSION:runtime) which has a
classifier runtime.
- With Maven 3.2.0 the agent could be looked up (artifactMap.get)
with org.jacoco:org.jacoco.agent, the key in the map was GA.
- With Maven 3.2.0 the key is now GAC (org.jacoco:org.jacoco.agent:
runtime)
- So now you are forced to give the classifier as well for the lookup,
when doing this it will break backwards compatibility.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Feb 11, 2014 at 4:42 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
not sure what's happening here. There seems to be a regression with
the jacoco-maven-plugin (works fine with Maven 3.0.2 and Maven 3.1.1).
What I did:
- Checked out https://github.com/1and1/testlink-junit
- Now running mvn320 -V -e clean verify gives the following:
12670 [ERROR] Failed to execute goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed. NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:
prepare-agent
(default-prepare-agent) on project tljunit-surefire: Execution
default-prepare-agent of goal
org.jacoco:jacoco-maven-plugin:0.6.4.201312101107:prepare-agent
failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:224)
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:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.
SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.
execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.
launchEnhanced(Launcher.java:289)
at
Re: [VOTE] Release Maven 3.2.0
On Wed, 12 Feb 2014 00:29:58 + Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hurrah! At last! (at least until the there must be a .0 release or the world will end gang on the PMC bash us back to 3.2.0) Stephen, I won't survive a none .0 version, what do I tell to my devs buddies ? :D At least, I will save me 2 hours finding back why I had a 3.1.1 on a server buggy with android plugin, just beacuse this was not the good 3.1.1 version ;) Shame on me to test not final maven version ;). Nice decision guys to move forward. +1 And viva then maven 3.2.1 \o/ tony. -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.0
3.2.0.1 :-) On Tue, Feb 11, 2014 at 7:42 PM, Tony Chemit che...@codelutin.com wrote: On Wed, 12 Feb 2014 00:29:58 + Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hurrah! At last! (at least until the there must be a .0 release or the world will end gang on the PMC bash us back to 3.2.0) Stephen, I won't survive a none .0 version, what do I tell to my devs buddies ? :D At least, I will save me 2 hours finding back why I had a 3.1.1 on a server buggy with android plugin, just beacuse this was not the good 3.1.1 version ;) Shame on me to test not final maven version ;). Nice decision guys to move forward. +1 And viva then maven 3.2.1 \o/ tony. -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] [CANCELLED] Release Maven 3.2.0
Does this mean Maven will now require Java 7 as the running JVM? Oddly - I don't see any close() method mentioned on: http://docs.oracle.com/javase/7/docs/api/java/lang/ClassLoader.html anywhere? On 12 Feb 2014, at 12:20, Stuart McCulloch wrote: I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. This happens after the Maven build is finished, but before JVM shutdown hooks run. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] [CANCELLED] Release Maven 3.2.0
Glad I wasn't the only one confused. Still, as I mention in my other post on this - does this not now mean that Maven MUST run on JDK7? Mark On 12 Feb 2014, at 12:41, Igor Fedorenko wrote: http://download.java.net/jdk8/docs/api/java/net/URLClassLoader.html -- Regards, Igor On 2/11/2014, 18:38, Laird Nelson wrote: On Tue, Feb 11, 2014 at 3:20 PM, Stuart McCulloch mccu...@gmail.com wrote: I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. Just as an aside, this sent me scrambling to my Javadocs; I see no such close() method on ClassLoader in any version of Java? (See for example http://download.java.net/jdk8/docs/api/java/lang/ClassLoader.html) Typo? Best, Laird - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.0
On 12 Feb 2014, at 13:57, Benson Margulies wrote: 3.2.0.1 :-) 3.2.0-patchlevel-1-GA. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] [CANCELLED] Release Maven 3.2.0
No, Maven will (correctly) close URLClassLoaders on java7 and will continue to work as before on older JVMs. Here is the code that implements this logic https://github.com/sonatype/plexus-classworlds/blob/master/src/main/java/org/codehaus/plexus/classworlds/ClassWorld.java#L110 -- Regards, Igor On 2/11/2014, 21:02, Mark Derricutt wrote: Does this mean Maven will now require Java 7 as the running JVM? Oddly - I don't see any close() method mentioned on: http://docs.oracle.com/javase/7/docs/api/java/lang/ClassLoader.html anywhere? On 12 Feb 2014, at 12:20, Stuart McCulloch wrote: I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. This happens after the Maven build is finished, but before JVM shutdown hooks run. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] [CANCELLED] Release Maven 3.2.0
On 12 February 2014 13:03, Mark Derricutt m...@talios.com wrote: Glad I wasn't the only one confused. Still, as I mention in my other post on this - does this not now mean that Maven MUST run on JDK7? nope there is a check here https://github.com/sonatype/plexus-classworlds/blob/master/src/main/java/org/codehaus/plexus/classworlds/realm/ClassRealm.java#L63 To know if the current class support the interface or not (a sort of isJdk1.7 autodetect) Mark On 12 Feb 2014, at 12:41, Igor Fedorenko wrote: http://download.java.net/jdk8/docs/api/java/net/URLClassLoader.html -- Regards, Igor On 2/11/2014, 18:38, Laird Nelson wrote: On Tue, Feb 11, 2014 at 3:20 PM, Stuart McCulloch mccu...@gmail.com wrote: I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. Just as an aside, this sent me scrambling to my Javadocs; I see no such close() method on ClassLoader in any version of Java? (See for example http://download.java.net/jdk8/docs/api/java/lang/ClassLoader.html) Typo? Best, Laird - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] [CANCELLED] Release Maven 3.2.0
Good to know :) On 12 Feb 2014, at 15:06, Igor Fedorenko wrote: No, Maven will (correctly) close URLClassLoaders on java7 and will continue to work as before on older JVMs. Here is the code that implements this logic - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: How to skip the execution of batch file based on need in maven build
Remove the phase element from the execution. William On Mon, Feb 10, 2014 at 11:12 PM, indira indira.kur...@gmail.com wrote: Added exec-maven-plugin pulgin in pom.xml plugins . plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId version1.2/version executions execution idrunbatchfile/id phasepackage/phase goals goalexec/goal /goals /execution /executions configuration executabletest.bat/executable /configuration /plugin /plugins When I execute the cmd 'mvn clean install' my bat file test.bat is getting executed. I wanted to execute the batch file on need basis. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-skip-the-execution-of-batch-file-based-on-need-in-maven-build-tp5783909.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
