[jira] Commented: (MNG-2811) issue description: 'Plugin dependencies override maven core artifacts causing NoClassDefFoundErrors'
[ http://jira.codehaus.org/browse/MNG-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158483#action_158483 ] Brett Porter commented on MNG-2811: --- David, do you still see this in recent versions of Maven? issue description: 'Plugin dependencies override maven core artifacts causing NoClassDefFoundErrors' - Key: MNG-2811 URL: http://jira.codehaus.org/browse/MNG-2811 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.4 Environment: OS agnostic, maven 2.0.4, jdk1.5 Reporter: David J. M. Karlsen Priority: Blocker Fix For: Reviewed Pending Version Assignment Attachments: 17artifactmultibulid.run1.log, 4artifact.filtered.log Usecase: wipe the local .m2 repo totally away. (rm -rf ~/.m2/repository) do a: mvn -X clean deploy site-deploy. Attached is the output from two different projects (one is a 4 artifact project - including the top pom, the other is a multibuild of 17 artifacts, also including top-pom). If I just re-run the mvn -X clean deploy site-deploy the builds will eventually succeed. I'll try to narrow down the pom's to pin down the failure with as little dependencies and plugins in action as possible - but this will take some time. I can be pinged at da...@codehaus.org or da...@davidkarlsen.com for re-running builds if needed. The logs are a little anonymized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2811) issue description: 'Plugin dependencies override maven core artifacts causing NoClassDefFoundErrors'
[ http://jira.codehaus.org/browse/MNG-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88485 ] David J. M. Karlsen commented on MNG-2811: -- It should be added that this also happens with maven 2.0.5 - could somebody with edit credentials update the issue? issue description: 'Plugin dependencies override maven core artifacts causing NoClassDefFoundErrors' - Key: MNG-2811 URL: http://jira.codehaus.org/browse/MNG-2811 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.4 Environment: OS agnostic, maven 2.0.4, jdk1.5 Reporter: David J. M. Karlsen Priority: Blocker Attachments: 17artifactmultibulid.run1.log, 4artifact.filtered.log Usecase: wipe the local .m2 repo totally away. (rm -rf ~/.m2/repository) do a: mvn -X clean deploy site-deploy. Attached is the output from two different projects (one is a 4 artifact project - including the top pom, the other is a multibuild of 17 artifacts, also including top-pom). If I just re-run the mvn -X clean deploy site-deploy the builds will eventually succeed. I'll try to narrow down the pom's to pin down the failure with as little dependencies and plugins in action as possible - but this will take some time. I can be pinged at [EMAIL PROTECTED] or [EMAIL PROTECTED] for re-running builds if needed. The logs are a little anonymized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2811) issue description: 'Plugin dependencies override maven core artifacts causing NoClassDefFoundErrors'
[ http://jira.codehaus.org/browse/MNG-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88490 ] David J. M. Karlsen commented on MNG-2811: -- and this only happens when calling the site goal issue description: 'Plugin dependencies override maven core artifacts causing NoClassDefFoundErrors' - Key: MNG-2811 URL: http://jira.codehaus.org/browse/MNG-2811 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.4 Environment: OS agnostic, maven 2.0.4, jdk1.5 Reporter: David J. M. Karlsen Priority: Blocker Attachments: 17artifactmultibulid.run1.log, 4artifact.filtered.log Usecase: wipe the local .m2 repo totally away. (rm -rf ~/.m2/repository) do a: mvn -X clean deploy site-deploy. Attached is the output from two different projects (one is a 4 artifact project - including the top pom, the other is a multibuild of 17 artifacts, also including top-pom). If I just re-run the mvn -X clean deploy site-deploy the builds will eventually succeed. I'll try to narrow down the pom's to pin down the failure with as little dependencies and plugins in action as possible - but this will take some time. I can be pinged at [EMAIL PROTECTED] or [EMAIL PROTECTED] for re-running builds if needed. The logs are a little anonymized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2811) issue description: 'Plugin dependencies override maven core artifacts causing NoClassDefFoundErrors'
[
http://jira.codehaus.org/browse/MNG-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86956
]
Kenney Westerhof commented on MNG-2811:
---
It looks like the dependencies brought in by the plugin (maven-model,
plexus-utils) are not filtered out the plugin's classrealm.
Since the conflict resolution in 2.0.4 bugs ('nearer found' is reported even
for dependencies at the same level, sometimes
causing older versions to replace newer onces), older versions of maven-model
etc. could be used, but these should've
been filtered out using the artifact filters since they're core artifacts.
This normally works but maybe the downloading of plugins disrupts this.
issue description: 'Plugin dependencies override maven core artifacts
causing NoClassDefFoundErrors'
-
Key: MNG-2811
URL: http://jira.codehaus.org/browse/MNG-2811
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0.4
Environment: OS agnostic, maven 2.0.4, jdk1.5
Reporter: David J. M. Karlsen
Priority: Blocker
Attachments: 17artifactmultibulid.run1.log, 4artifact.filtered.log
Usecase:
wipe the local .m2 repo totally away. (rm -rf ~/.m2/repository)
do a:
mvn -X clean deploy site-deploy.
Attached is the output from two different projects (one is a 4 artifact
project - including the top pom, the other is a multibuild of 17 artifacts,
also including top-pom).
If I just re-run the mvn -X clean deploy site-deploy the builds will
eventually succeed.
I'll try to narrow down the pom's to pin down the failure with as little
dependencies and plugins in action as possible - but this will take some time.
I can be pinged at [EMAIL PROTECTED] or [EMAIL PROTECTED] for re-running
builds if needed.
The logs are a little anonymized.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
