[
http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108069
]
Jason van Zyl commented on MNG-1323:
------------------------------------
I have reverted this change:
svn merge -r575987:575986
https://svn.apache.org/repos/asf/maven/components/trunk .
As it was breaking trunk horribly. My theory is that I had everything locally
required to make it work. Piotr, you'll have to look at you get a
PluginDescriptor not found error for tons of plugins which isn't right.
> 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-components-2.0.x.diff,
> MNG-1323-core-integration-testing-2.diff,
> MNG-1323-core-integration-testing.diff,
> MNG-1323-core-integration-tests-3.diff, MNG-1323-core-integration-tests.diff,
> MNG1323-maven-core-2.1.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
