You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2006/11/02 17:02:08 UTC

[jira] Updated: (MNG-1962) allow empty deprecation messages in plugin descriptor/annotation and document usage of deprecation in descriptor/annotation.

     [ http://jira.codehaus.org/browse/MNG-1962?page=all ]

Kenney Westerhof updated MNG-1962:
----------------------------------

    Fix Version/s:     (was: 2.0.5)
                   2.0.6

> allow empty deprecation messages in plugin descriptor/annotation and document usage of deprecation in descriptor/annotation.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-1962
>                 URL: http://jira.codehaus.org/browse/MNG-1962
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Documentation:  General, Plugin Creation Tools
>    Affects Versions: 2.0.1
>            Reporter: John Casey
>            Priority: Minor
>             Fix For: 2.0.6
>
>
> currently, the deprecation features for plugins (not the java deprecation mechanism, necessarily) require a message for the deprecation warning to be printed. This point is poorly documented.
> Allow an empty deprecation message (make one up when the plugin descriptor is read, if the <deprecation/> element is present but empty), and then document the usage of plugin deprecations at the class and parameter level.

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