Re: [PLEASE TEST] Apache Maven 3.0-RC1
lukewpatterson wrote: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintjar/role-hint Before, it seems the custom goals were merged with the standard jar packaging goals. If you can provide a complete example project to show this merging I would be really surprised. AFAICT from my own testing, it's simply impossible for a plugin to contribute a custom lifecycle mapping that clashes with a built-in mapping in Maven 2.x. I.e. your mapping should get ignored and Maven continues to use the default jar mapping. Now, it seems like they replace the standard goals. Which is the expected behavior, the mapping is supposed to be a full self-contained description, not an overlay. Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Benjamin Bentmann wrote: lukewpatterson wrote: Before, it seems the custom goals were merged with the standard jar packaging goals. If you can provide a complete example project to show this merging I would be really surprised. lukewpatterson wrote: Now, it seems like they replace the standard goals. Which is the expected behavior, the mapping is supposed to be a full self-contained description, not an overlay. Thanks Benjamin, everything is working ok. This was an example of a sleeper-corner-case mixed with a healthy does of ignorance. The custom jar packaging type was indeed never active with Maven 2.x, I have no idea why it existed in that plugin's metadata and I have no idea why it was enabled in the consumer via extension. The overlay behavior was simply other plugins running which were explicitly bound to phases. I forgot that the other phases exist regardless of whether or not they are listed in the custom lifecycle mappings. Thanks for your help. Other than that, everything works great, and seems to be about 33% faster overall. -- View this message in context: http://maven.40175.n5.nabble.com/PLEASE-TEST-Apache-Maven-3-0-RC1-tp2841339p2848218.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Seeing different behavior around extensions enabled on jar custom packaging type. Using a testing plugin which contains jar as a custom packaging type. From the plugin's components.xml: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintjar/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases testsome.groupId:some-plugin:run-tests/test /phases Did something change/become-fixed around this scenario? Before, it seems the custom goals were merged with the standard jar packaging goals. Now, it seems like they replace the standard goals. I haven't had time to investigate enough to determine if that description is fully accurate, but that's what it seems like so far. I noticed the behavior when the testing plugin said it didn't have any tests to run. Finally I figured out that the compile goals were never run, which meant the the .class files were never written, which meant the testing plugin didn't have any .class files to run. -- View this message in context: http://maven.40175.n5.nabble.com/PLEASE-TEST-Apache-Maven-3-0-RC1-tp2841339p2847303.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Hi guys, so far so good, but I've found something little odd. I have reporting plugins preconfigured in pluginManagement section of parent pom and I've noticed that this configuration is used only when building parent and is not inherited into child projects and has to be configured explicitly again. Version of plugin is inherited. Is it intentional? Martin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Still not seeing the promised speed up when on a mac (and actually always a bit slower). But definitely seeing the improved times on a linux box (Linux 2.6.32-24-server #41-Ubuntu x86_64 GNU/Linux ) So it seems that if you are on a mac then be aware that upgrading to mvn 3 could at best give you the same build times as mvn 2 and at worst be a tad slower out of the box. If you run with -T options it seems to deliver on performance. The typical build times with mvn 2 are: Linux: Total time: 57 seconds (always 1m) Mac: Total time: 1 minute 11 seconds (usually around this time +-5 seconds) Initial build times using Apache Maven 3.0-RC1 (r997478; 2010-09-15 14:57:55-0500) Linux: Total time: 1:53.554s Mac: Total time: 1:56.945s Subsequent build times: Linux: Total time: 48.646s Mac: Total time: 1:20.053s I'm only added the last run of 3 from each since the runs were all pretty close. This was tested on 2 different macs but only 1 linux box (which is a hefty box so the times are a bit unfair towards the linux box). Running with -T 1c brings the mac builds under a minute (2 cores on the macs). Mac: Total time: 58.675s (Wall Clock) And an astounding 1/2 time builds on the linux box (8 cores) Linux: Total time: 32.193s (Wall Clock) On Wed, Sep 15, 2010 at 3:34 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
So now I've found most likely bug in site plugins configuration
In parent pom.xml
build.pluginManagement.plugins.plugin[maven-site-plugin].reportPlugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
reports
reportchanges-report/report
/reports
configuration
xmlPath${basedir}/src/changes.xml/xmlPath
/configuration
/plugin
plugin
groupIdde.smartics.maven.plugin/groupId
artifactIdmaven-buildmetadata-plugin/artifactId
reports
reportbuildmetadata-report/report
/reports
/plugin
If in child pom.xml
build.pluginManagement.plugins.plugin[maven-site-plugin].reportPlugins
plugin
groupIdde.smartics.maven.plugin/groupId
artifactIdmaven-buildmetadata-plugin/artifactId
!--
reports
reportbuildmetadata-report/report
/reports
--
/plugin
same maven-buildmetadata-plugin is without
reportbuildmetadata-report/report mvn site will fail
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site
(default-site) on project komix-common: failed to
get Reports: Could not find goal changes-report in plugin
de.smartics.maven.plugin:maven-buildmetadata-plugin:1.1.0 among
available goals bu
ildmetadata-report, provide-buildmetadata, build-point - [Help 1]
So it tries to generate report from another plugin...
It fails in combinations:
parent in build.pluginManagement child in build.pluginManagement
parent in build.pluginManagement child in build.plugins
parent in build.plugins child in build.plugins
So it only works when:
parent in build.plugins child in build.pluginManagement because child
build.pluginManagement is completely ignored (and it is inherited) for
site plugin
Hi guys,
so far so good, but I've found something little odd.
I have reporting plugins preconfigured in pluginManagement section of
parent pom and I've noticed that this configuration is used only when
building parent and is not inherited into child projects and has to be
configured explicitly again. Version of plugin is inherited. Is it
intentional?
Martin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Hi,
Here it's more a site plugin issue (looks related to
http://jira.codehaus.org/browse/MSITE-504 but needs to be more
investigated)
Can you record an issue with a simple project to reproduce ?
Thanks,
2010/9/17 Martin Vaněk antha...@post.cz:
So now I've found most likely bug in site plugins configuration
In parent pom.xml
build.pluginManagement.plugins.plugin[maven-site-plugin].reportPlugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
reports
reportchanges-report/report
/reports
configuration
xmlPath${basedir}/src/changes.xml/xmlPath
/configuration
/plugin
plugin
groupIdde.smartics.maven.plugin/groupId
artifactIdmaven-buildmetadata-plugin/artifactId
reports
reportbuildmetadata-report/report
/reports
/plugin
If in child pom.xml
build.pluginManagement.plugins.plugin[maven-site-plugin].reportPlugins
plugin
groupIdde.smartics.maven.plugin/groupId
artifactIdmaven-buildmetadata-plugin/artifactId
!--
reports
reportbuildmetadata-report/report
/reports
--
/plugin
same maven-buildmetadata-plugin is without
reportbuildmetadata-report/report mvn site will fail
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-site) on
project komix-common: failed to
get Reports: Could not find goal changes-report in plugin
de.smartics.maven.plugin:maven-buildmetadata-plugin:1.1.0 among available
goals bu
ildmetadata-report, provide-buildmetadata, build-point - [Help 1]
So it tries to generate report from another plugin...
It fails in combinations:
parent in build.pluginManagement child in build.pluginManagement
parent in build.pluginManagement child in build.plugins
parent in build.plugins child in build.plugins
So it only works when:
parent in build.plugins child in build.pluginManagement because child
build.pluginManagement is completely ignored (and it is inherited) for site
plugin
Hi guys,
so far so good, but I've found something little odd.
I have reporting plugins preconfigured in pluginManagement section of
parent pom and I've noticed that this configuration is used only when
building parent and is not inherited into child projects and has to be
configured explicitly again. Version of plugin is inherited. Is it
intentional?
Martin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Olivier
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
+1 (non-binding) Tested corporate and oss projects. Did not test the release process. /Paul Quoting Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/mav en/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+N otes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversi on=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
+1, no problem. Tested multimodules build, on windows and AIX (ibm jvm), with and without // build activated. Congratulations for the work! 2010/9/16 Paul Merlin eska...@n0pe.org +1 (non-binding) Tested corporate and oss projects. Did not test the release process. /Paul Quoting Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/mav en/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+N otes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversi on=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [PLEASE TEST] Apache Maven 3.0-RC1
I have a plugin where I use the maven3 api. maven-beta-2, maven-beta-1, maven-alpha-6/7, worked maven-beta-3 gives Caused by: java.lang.NullPointerException at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:185) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:175) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:237) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:219) maven-RC1 gives Caused by: java.lang.NoSuchMethodError: org.apache.maven.project.ProjectBuildingRequest.setForceUpdate(Z)Lorg/apache/maven/project/ProjectBuildingRequest; maybe I should not have used that ProjectBuilder, maybe that is not part of the public API, maybe I am the only one writing plugin with maven3 API - then never mind I fix it on my side. regards Kristian On Thu, Sep 16, 2010 at 3:13 PM, Baptiste MATHUS m...@batmat.net wrote: +1, no problem. Tested multimodules build, on windows and AIX (ibm jvm), with and without // build activated. Congratulations for the work! 2010/9/16 Paul Merlin eska...@n0pe.org +1 (non-binding) Tested corporate and oss projects. Did not test the release process. /Paul Quoting Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/mav en/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+N otes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversi on=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
kristian wrote: I have a plugin where I use the maven3 api. maven-RC1 gives Caused by: java.lang.NoSuchMethodError: org.apache.maven.project.ProjectBuildingRequest.setForceUpdate(Z)Lorg/apache/maven/project/ProjectBuildingRequest; maybe I should not have used that ProjectBuilder, maybe that is not part of the public API Usage of the ProjectBuilder in general is fine, but the request object needed to change. So yes, please update your plugin to adopt the API in the RC. Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
I've tested a multimodule build, on ubuntu 10.04. The build ran fine, except the warnings complaining about the missing versions of the plugins inside build/plugins: [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-war-plugin is missing. [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-resources-plugin is missing. and about my parameterized artifact version: [WARNING] 'version' contains an expression but should be a constant. Well, those warnings are a little bit annoying, although the build ran successfully. But, at the end, I''ll keep on using the 2.2.1 version, cause I'm not going through all my poms setting plugins versions and I need to keep my projects version parameterized. On Thu, Sep 16, 2010 at 6:43 AM, Baptiste MATHUS m...@batmat.net wrote: +1, no problem. Tested multimodules build, on windows and AIX (ibm jvm), with and without // build activated. Congratulations for the work! 2010/9/16 Paul Merlin eska...@n0pe.org +1 (non-binding) Tested corporate and oss projects. Did not test the release process. /Paul Quoting Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/mav en/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+N otes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversi on=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Benjamin I just found this problem : http://jira.codehaus.org/browse/MNG-4813 It is failing for all alpha/beta I tested thus it isn't a problem in RC itself. It occurs with an old version of the jdocbook plugin we are always using in GateIn and few others projects. Arnaud Héritier Software Factory Manager http://www.exoplatform.com Phone : +33 (0)6 89 74 64 24 Skype : aheritier Twitter : @aheritier Blog : http://aheritier.net On Sep 15, 2010, at 10:34 PM, Benjamin Bentmann wrote: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[PLEASE TEST] Apache Maven 3.0-RC1
Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
