[ 
http://jira.codehaus.org/browse/MPLUGIN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Bentmann moved MNG-1889 to MPLUGIN-103:
------------------------------------------------

    Affects Version/s:     (was: 2.0.1)
                       2.3
        Fix Version/s:     (was: 2.0.7)
                       2.4
          Component/s:     (was: Sites & Reporting)
                       API
                  Key: MPLUGIN-103  (was: MNG-1889)
              Project: Maven 2.x Plugin Tools  (was: Maven 2)

> Plugins without descriptors
> ---------------------------
>
>                 Key: MPLUGIN-103
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-103
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 2.3
>            Reporter: Jochen Wiedmann
>            Priority: Minor
>             Fix For: 2.4
>
>         Attachments: maven-no-plugin-descriptors.patch, 
> numMojoDescriptors.patch
>
>
> The attached patch throws an exception, if no Mojos are found in a plugin.
> Background: If such a plugin is installed, then an NPE is caused in the 
> DefaultLifeCycleExecutor, which properly assumes, that a plugin contains Mojo 
> descriptors. Obviously, the actual error is in the plugin itself, where it 
> should be exposed. It took me some hours to find this actual reason. (I still 
> do not know, why the Mojos aren't found in my plugin, but that's another 
> story.) The patch should be able to save the same number of hours for other 
> plugin developers.
> Note: The InvalidPluginDescriptorException, which is triggered by the patch, 
> is possibly not proper. I choosed it, because it allowed to leave the method 
> signature unchanged and keep the patch simple. It is up to the reviewer to 
> choose another exception.

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