[
http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105832
]
Mikko Koponen commented on MNG-1323:
------------------------------------
Ugliest workaround yet:
Since we are mostly running into this when using the maven-antrun-plugin, I
redeployed the version we are using into our company-wide maven repo with a
different groupId/artifactId, and am now issueing such groupIds/artifactIds to
developers that require differing dependencies in their antruns. When this bug
gets fixed, I'll relocate all those plugins back to the real version.
> Plugin extensions (dependencies) not resolved in reactor build
> --------------------------------------------------------------
>
> Key: MNG-1323
> URL: http://jira.codehaus.org/browse/MNG-1323
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0
> Reporter: Kenney Westerhof
> Fix For: 2.0.x
>
> Attachments: MNG-1323-core-integration-tests.diff
>
>
> I've added a dependency on an Ant Task in
> project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/
> and run that anttask using the antrun plugin.
> When run from the project dir itself it runs fine.
> When running from the root of the project tree (reactor build, project one
> level below root),
> antrun bails out because the taskdef can't be found (not on classpath).
> It looks like the dependency isn't resolved, or not added to the plugins'
> classrealm.
--
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
