You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kohsuke Kawaguchi (JIRA)" <ji...@codehaus.org> on 2007/04/03 22:25:20 UTC
[jira] Created: (MPLUGIN-32) Make it an error for a plugin to have
no mojo
Make it an error for a plugin to have no mojo
---------------------------------------------
Key: MPLUGIN-32
URL: http://jira.codehaus.org/browse/MPLUGIN-32
Project: Maven 2.x Plugin Plugin
Issue Type: Improvement
Reporter: Kohsuke Kawaguchi
Maven plugins must have mojos to be useful, and not having a mojo causes a problem down the line like MNG-2925.
Therefore it would be desirable for the plugin plugin to check for this and issue an error, so that errors will be caught early, not later. A silly pom mistake (such as not setting build/sourceDirectory right) causes this kind of problems.
--
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
[jira] Commented: (MPLUGIN-32) Make it an error for a plugin to
have no mojo
Posted by "Heinrich Nirschl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118367 ]
Heinrich Nirschl commented on MPLUGIN-32:
-----------------------------------------
A maven archetype technically is a plugin without a mojo.
> Make it an error for a plugin to have no mojo
> ---------------------------------------------
>
> Key: MPLUGIN-32
> URL: http://jira.codehaus.org/browse/MPLUGIN-32
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Reporter: Kohsuke Kawaguchi
>
> Maven plugins must have mojos to be useful, and not having a mojo causes a problem down the line like MNG-2925.
> Therefore it would be desirable for the plugin plugin to check for this and issue an error, so that errors will be caught early, not later. A silly pom mistake (such as not setting build/sourceDirectory right) causes this kind of problems.
--
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
[jira] Closed: (MPLUGIN-32) Make it an error for a plugin to have
no mojo
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MPLUGIN-32.
----------------------------
Assignee: Brian Fox
Resolution: Duplicate
Fix Version/s: 2.4
> Make it an error for a plugin to have no mojo
> ---------------------------------------------
>
> Key: MPLUGIN-32
> URL: http://jira.codehaus.org/browse/MPLUGIN-32
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Reporter: Kohsuke Kawaguchi
> Assignee: Brian Fox
> Fix For: 2.4
>
>
> Maven plugins must have mojos to be useful, and not having a mojo causes a problem down the line like MNG-2925.
> Therefore it would be desirable for the plugin plugin to check for this and issue an error, so that errors will be caught early, not later. A silly pom mistake (such as not setting build/sourceDirectory right) causes this kind of problems.
--
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