Build ecChronos With Java 17 - Issue #607 #617
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tommystendahl
requested review from
ch1bbe,
tommystendahl,
jwaeab and
masokol
jwaeab
approved these changes
Nov 27, 2023
jwaeab
previously approved these changes
Dec 1, 2023
VictorCavichioli
force-pushed
the
support-java-17
branch
3 times, most recently
from
7276b34 to
840874e
Compare
Closed
|
I don't think we should drop java11 support yet. It would be great if we could support both java 11 and java 17. |
|
Any decision on this one? |
VictorCavichioli
force-pushed
the
support-java-17
branch
from
cc29eee to
ea64030
Compare
|
After some more discussions, we saw that we cannot release with an alpha version, even if it's just for testing, so as the fix for jamm was done in version 5 we will wait for an stable release to keep working on this, related issue: https://issues.apache.org/jira/browse/CASSANDRA-16304 |
VictorCavichioli
force-pushed
the
support-java-17
branch
2 times, most recently
from
2b2fe7d to
c511360
Compare
In order to provide support for Java 17 in EcChronos, identify the minimal changes necessary for the project to compile and run with Java 17. Additionally, implement these changes and any necessary updates to Maven packages. This change must be merged just after a release of ecChronos with the Issue Ericsson#616 done. Closes Ericsson#607
In order to provide support for Java 17 in EcChronos, identify the minimal changes necessary for the project to compile and run with Java 17. Additionally, implement these changes and any necessary updates to Maven packages. This change must be merged just after a release of ecChronos with the Issue Ericsson#616 done. Closes Ericsson#607
In order to provide support for Java 17 in EcChronos, identify the minimal changes necessary for the project to compile and run with Java 17. Additionally, implement these changes and any necessary updates to Maven packages. This change must be merged just after a release of ecChronos with the Issue Ericsson#616 done. Closes Ericsson#607
In order to provide support for Java 17 in EcChronos, identify the minimal changes necessary for the project to compile and run with Java 17. Additionally, implement these changes and any necessary updates to Maven packages. This change must be merged just after a release of ecChronos with the Issue Ericsson#616 done. Closes Ericsson#607
VictorCavichioli
force-pushed
the
support-java-17
branch
from
31e6994 to
7cb8724
Compare
tommystendahl
approved these changes
Sep 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to provide support for Java 17 in EcChronos, identify the minimal changes necessary for the project to compile and run with Java 17. Additionally, implement these changes and any necessary updates to Maven packages.
This change must be merged just after a release of ecChronos with the Issue #616 done.
Closes #607