Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
5.0-alpha2, 5.0, 5.1
-
Code Clarity
-
Normal
-
All
-
None
-
Description
It would be great if we introduced in 5.0 a change in Deprecated annotations like this:
@Deprecated(since = "4.0")
or
@Deprecated(since = "3.11")
The reasoning behind this is that as of now, it is pretty cumbersome to figure out what can be removed on the next major version. It has to be, basically, done manually every time.
There is also this parameter available:
@Deprecated(forRemoval = true / false)
which indicates whether the annotated element is subject to removal in a future version so we do not need to think about this every time if it is eligible for deletion in a next major or not.
We could then have a check which would ensure that we are not releasing a next major with some deprecations introduced two majors before.