[ 
http://jira.codehaus.org/browse/MNG-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201209#action_201209
 ] 

Laird Nelson commented on MNG-4479:
-----------------------------------

Quite right of course.  See attachment.  Now hopefully it won't hang around for 
quite some time!  :-)

> Dependency resolution for plugins with default-cli execution happens too late
> -----------------------------------------------------------------------------
>
>                 Key: MNG-4479
>                 URL: http://jira.codehaus.org/browse/MNG-4479
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Class Loading, Dependencies, Plugins and Lifecycle
>    Affects Versions: 2.2.1
>            Reporter: Laird Nelson
>         Attachments: mng-4479.zip
>
>
> I have a plugin that makes use of the implementation attribute in its 
> configuration.  That is, one of its parameters is a plexus tag that specifies 
> an implementation class to use.
> The implementation class comes from a jar that is the plugin's dependency, 
> but that dependency is included as part of the plugin configuration, not as 
> part of the stock plugin.
> This setup works fine when I bind the plugin's configuration via an execution 
> to a normal phase (generate-sources as it happens).
> When I bind the plugin's configuration to the default-cli execution, plexus 
> cannot configure the component, claiming that the classname it encounters in 
> the "implementation" attribute cannot be found (even though, again, if I bind 
> it to the generate-sources phase instead, via another execution, same 
> configuration, everything works fine.
> I tried to debug this using mvn -X, but the output was totally baffling; 
> sorry.  My raw take is that it looks like dependency resolution in the 
> default-cli execution is somehow performed differently than when the plugin 
> is run bound to a phase.

-- 
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

        

Reply via email to