You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Fredrik Vraalsen (JIRA)" <ji...@codehaus.org> on 2006/07/06 12:31:23 UTC
[jira] Commented: (MDEP-7) [dependency-maven-plugin]
ClassCastException caused by DefaultArtifact vs. ActiveProjectArtifact
[ http://jira.codehaus.org/browse/MDEP-7?page=comments#action_69055 ]
Fredrik Vraalsen commented on MDEP-7:
-------------------------------------
I'm also seeing this problem in the 2.0-SNAPSHOT version of the maven-dependency-plugin during a multiproject build. The patch already attached to this issue fixes the problem for me.
> [dependency-maven-plugin] ClassCastException caused by DefaultArtifact vs. ActiveProjectArtifact
> ------------------------------------------------------------------------------------------------
>
> Key: MDEP-7
> URL: http://jira.codehaus.org/browse/MDEP-7
> Project: Maven 2.x Dependency Plugin
> Type: Bug
> Reporter: Christian Schulte
> Assignee: Brian Fox
> Priority: Trivial
> Attachments: ActiveProjectArtifact.patch
>
>
> I reproducible got a ClassCastException during copy-dependencies goal. There is a cast to DefaultArtifact which fails if the actual instance is ActiveProjectArtifact which does not extend DefaultArtifact. After patching the plugin and trying the old version again to verify reproducibility the exception magically never appeared again so I cannot reproduce the stacktrace somehow. However, the cast to DefaultArtifact can be changed to Artifact, I think.
--
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