You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ludovic Claude (JIRA)" <ji...@codehaus.org> on 2008/04/02 17:32:58 UTC
[jira] Commented: (MPLUGIN-106) remove no mojo deprecation warning
and throw an exception
[ http://jira.codehaus.org/browse/MPLUGIN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129551#action_129551 ]
Ludovic Claude commented on MPLUGIN-106:
----------------------------------------
I've got some reservation on throwing an exception, see MPLUGIN-109. Basically, which packaging should I use for a Maven plugin which doesn't define any Mojo but define a custom packaging with Plexus?
> remove no mojo deprecation warning and throw an exception
> ---------------------------------------------------------
>
> Key: MPLUGIN-106
> URL: http://jira.codehaus.org/browse/MPLUGIN-106
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Affects Versions: 2.4.1
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 2.5
>
>
> MPLUGIN-103 (was MNG-1889) suddenly changed functionality that broke existing builds resulting in MPLUGIN-102. We restored the old functionality with a deprecation warning and commented out the test. Remove this in the next release and make it fail the build.
--
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