|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [mojo-dev] [jira] (MWEBMINI-11) Make the plugin wo... Lonny Jacobson (JIRA)
- [mojo-dev] [jira] (MWEBMINI-11) Make the plug... Christopher Hunt (JIRA)
- [mojo-dev] [jira] (MWEBMINI-11) Make the plug... Lonny Jacobson (JIRA)
- [mojo-dev] [jira] (MWEBMINI-11) Make the plug... Christopher Hunt (JIRA)
- [mojo-dev] [jira] (MWEBMINI-11) Make the plug... Christopher Hunt (JIRA)
- [mojo-dev] [jira] (MWEBMINI-11) Make the plug... Lonny Jacobson (JIRA)
- [mojo-dev] [jira] (MWEBMINI-11) Make the plug... Christopher Hunt (JIRA)
- [mojo-dev] [jira] (MWEBMINI-11) Make the plug... Christopher Hunt (JIRA)
- [mojo-dev] [jira] (MWEBMINI-11) Make the plug... Christopher Hunt (JIRA)
Fair enough. I've never written a Maven plugin so I don't know what information is available to a plugin. You could add a read-only parameter that defaults to $
{project.packaging}. After doing some research, you can access the MavenProject in the plugin context map. This class has a getPackaging() method that returns the same value.