-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs: clarify deprecation of RELEASE and LATEST version constants #11686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
The |
|
Thanks for the clarification. I misunderstood the deprecation timeline for
LATEST and RELEASE. I’ll close this PR accordingly.
…On Fri, Jan 30, 2026 at 1:32 AM Tamas Cservenak ***@***.***> wrote:
*cstamas* left a comment (apache/maven#11686)
<#11686 (comment)>
The LATEST and RELEASE meta versions have been deprecated since Maven
3.0, this change is incorrect.
—
Reply to this email directly, view it on GitHub
<#11686 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BV47V2RK2T7C3COCPRGCAG34JJRN7AVCNFSM6AAAAACTLJ7KHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRQGAYDSMZQGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Instead of closing the PR, maybe just replace it by the addition of the |
|
Thanks for the suggestion. I’ve updated the PR to add the correct |
|
|
||
| @Deprecated(since = "4.0.0") | ||
| /** | ||
| * @deprecated since 3.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to duplicate the since parameter
| @Deprecated(since = "4.0.0") | ||
| /** | ||
| * @deprecated since 3.0 | ||
| * Use a fixed version or an explicit version range instead of special version tokens. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
never use version ranges
What was done
Added JavaDoc guidance for deprecated artifact version constants to clarify recommended alternatives.
Why
The deprecated RELEASE and LATEST version tokens provided no migration guidance, which could confuse users.
Scope
Documentation-only change. No functional impact.