Skip to content

Conversation

@amahi1568
Copy link

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.

@cstamas
Copy link
Member

cstamas commented Jan 29, 2026

The LATEST and RELEASE meta versions have been deprecated since Maven 3.0, this change is incorrect.

@amahi1568
Copy link
Author

amahi1568 commented Feb 1, 2026 via email

@desruisseaux
Copy link
Contributor

Instead of closing the PR, maybe just replace it by the addition of the since = "3.0" attribute in @Deprecated. It would avoid the same confusion to happen again.

@amahi1568
Copy link
Author

Thanks for the suggestion. I’ve updated the PR to add the correct
@deprecated(since = "3.0") attribute for RELEASE and LATEST constants,
so the deprecation timeline is clear and avoids future confusion.


@Deprecated(since = "4.0.0")
/**
* @deprecated since 3.0
Copy link
Contributor

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

never use version ranges

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants