[
https://issues.apache.org/activemq/browse/SM-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43443#action_43443
]
Steve Kondik commented on SM-1396:
----------------------------------
Looked into this a bit, and the fix is to simply add
org.apache.maven:maven-artifact explicitly as a dependency to the SM plugin.
Also, maven-plugin-tools-ant needs upgraded to 2.1 to build with Maven 2.0.9.
> NoSuchMethodException
> .ArtifactResolutionResult.setArtifactResolutionNodes(Ljava/util/Set;)V with
> M2Eclipse / Maven 2.1
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1396
> URL: https://issues.apache.org/activemq/browse/SM-1396
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Affects Versions: 3.2.1
> Reporter: Steve Kondik
>
> jbi-maven-plugin does not work with new versions of M2Eclipse (which uses
> Maven 2.1).
> An internal error occurred during: "Updating Maven Configuration".
> org.apache.servicemix.maven.plugin.jbi.GenerateComponentDescriptorMojo#execute()
> caused a linkage error (java.lang.NoSuchMethodError)
> org.apache.maven.artifact.resolver.ArtifactResolutionResult.setArtifactResolutionNodes(Ljava/util/Set;)V
> I've had a bug opened on M2Eclipse since last year regarding this:
> http://jira.codehaus.org/browse/MNGECLIPSE-415 but it doesn't seem to have
> gained any traction. It appears that maven-artifact-3.0-SNAPSHOT still
> contains the method so I am not sure what's going on here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
