-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Branch(java8): Add -legacy
version qualifier to java8 compatible modules
#2945
Branch(java8): Add -legacy
version qualifier to java8 compatible modules
#2945
Conversation
client-java-api
module to client-java-api-legacy
client-java-api
module to client-java-api-legacy
Suffix feels fine to me for now at least, if people complain we can always change it in future releases. |
Signed-off-by: Min Jin <[email protected]>
c7c35bf
to
fb59995
Compare
client-java-api
module to client-java-api-legacy
-legacy
version qualifier to java8 compatible modules
/hold cancel @brendandburns update the PR to add a
i suppose the new suffix conforms to the maven release version convention here: https://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns, yue9944882 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@brendandburns alternatively, do you think we should make these legacy java8-compatible codes a new module (specifically a new module name) or the same module name with a suffixed version e.g.
19.0.0.legacy
?