Description
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.
Attachments
Attachments
Issue Links
- is depended upon by
-
MPLUGIN-102 The 2.4 Release Breaks Previously-Working Builds
- Closed
- is duplicated by
-
MPLUGIN-32 Make it an error for a plugin to have no mojo
- Closed
- relates to
-
MPLUGIN-102 The 2.4 Release Breaks Previously-Working Builds
- Closed
-
MPLUGIN-106 remove no mojo deprecation warning and throw an exception
- Closed