You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2014/05/30 19:53:02 UTC

[jira] [Created] (LUCENE-5719) Add additional checks and enforcement around Deprecation to the build system.

Mark Miller created LUCENE-5719:
-----------------------------------

             Summary: Add additional checks and enforcement around Deprecation to the build system.
                 Key: LUCENE-5719
                 URL: https://issues.apache.org/jira/browse/LUCENE-5719
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Mark Miller


It would be great if we enforced a reasonable minimum for deprecation use.

Something like:

* Both the annotation and the comment should be required.
* Comment deprecation should require a comment.
* Annotation should require a JIRA url. (Doesn't seem we could do this nicely :( )

I run into, and perhaps even write, too many places with Deprecate and no helpful path or clue for the user and obviously Deprecation should be as non confusing as possible and polite deprecation enforced to the degree that we can do it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org