[
https://jira.codehaus.org/browse/MNG-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337167#comment-337167
]
Sascha Vujevic commented on MNG-5545:
-------------------------------------
Thank you for the reply, but i think this is not a satisfying answer.
I have looked at the maven-dependency-plugin, but i don't understand, why the
plugin is not using the org.sonatype.aether of the plugin.xml ?
It is searching the org.eclipse.aether of the maven installation instead. How
does this mechanism work ?
Sorry for the further question and thank you for your patience.
> NoClassDefFoundError:
> org/sonatype/aether/resolution/ArtifactResolutionException
> --------------------------------------------------------------------------------
>
> Key: MNG-5545
> URL: https://jira.codehaus.org/browse/MNG-5545
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies, Plugin API, POM
> Affects Versions: 3.1.0
> Environment: Windows XP
> Reporter: Sascha Vujevic
> Assignee: Robert Scholte
> Attachments: build.log, examplemojo.zip, mojocaller.zip
>
>
> Hello maven-developers,
> i hope this is the right tracker.
> I am implementing a mojo which uses classes from org.sonatype.aether.
> With maven 3.0.x the build succeeds, with maven 3.1.0 it breaks with error
> shown in the log-file.
> My question is, why the maven-build uses the org.eclipse.aether (still
> milestone) from the maven-installation (where org.sonatype.aether is not
> included) instead of useing it from the pluging.xml.
> The parameter @requiresDependencyResolution runtime seems not to work.
> I have attached the log-file and 2 projects, examplemojo is the mojo and
> mojocaller is the caller.
> Just install examplemojo and call "mvn call package on" mojocaller.
> Thank you for your help.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
