[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54948 ]
Brett Porter commented on MNG-1323:
---
workaround is to include the dependency in the first antrun plugin instance
encountered. one way to guarantee would be to include this in the root
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54941 ]
ruel loehr commented on MNG-1323:
-
Are there any suggested work arounds for this issue?Hence, if I wish to use
a custom ant task in a child module (which would require a dependency u
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54633 ]
Brett Porter commented on MNG-1323:
---
note above that this is scheduled for 2.0.3 (Feb release).
> Plugin extensions (dependencies) not resolved in reactor build
> -
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54612 ]
Georges Polyzois commented on MNG-1323:
---
Is this beeing resolved? I have exactly this problem as Kenney stated on
04/Nov/05.
I am using Maven 2.0.1 and even changed to using antru
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_50268 ]
John Casey commented on MNG-1323:
-
It looks like some of the work I did to get the ant-mojo support up and running
was related to this. Kenney's 04/Nov/2005 post was related to my fix fo
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_50020 ]
Brett Porter commented on MNG-1323:
---
did you test it with 2.0 or 2.0.1? Maybe this should be closed as cannot
reproduce?
> Plugin extensions (dependencies) not resolved in reactor bui
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_50012 ]
Kenney Westerhof commented on MNG-1323:
---
I don't think so - inheritance doesn't play a role. The parent-pom is just an
empty pom stating 1 module -> the pom discussed above.
I'll f
