[
https://issues.apache.org/jira/browse/SOLR-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103818#comment-17103818
]
Erick Erickson commented on SOLR-13138:
---------------------------------------
Here are some ideas I've been kicking around on deprecations (Gradle only).
Note, I'm currently working on compiler warnings (SOLR-10810), I want to start
working on deprecations after that's done.
- have the check or build fail once a project has been cleaned (not sure how
yet)
- adding a check on deprecated tags insuring that "as of" and "use XXX instead"
(or whatever we agree on for those two concepts) are recorded. It’s maddening
to see bare @deprecated annotations and then have to go hunt to see when the
hell that happened and what should be used instead.
> Remove deprecated code in master
> --------------------------------
>
> Key: SOLR-13138
> URL: https://issues.apache.org/jira/browse/SOLR-13138
> Project: Solr
> Issue Type: Improvement
> Affects Versions: master (9.0)
> Reporter: Alan Woodward
> Priority: Major
>
> There are a number of deprecations in master that should be removed. This
> issue is to keep track of deprecations as a whole, some individual
> deprecations may require their own issues.
>
> Work on this issue should be pushed to the `master-deprecations` branch on
> gitbox.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
