Skip to content

Restore Java 8 runtime compatibility #278

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

Closed
wants to merge 1 commit into from
Closed

Conversation

slachiewicz
Copy link
Member

Java 11 is required at runtime for:

aspectj 1.9.8+ requires Java 11
https://github.com/eclipse/org.aspectj/blob/master/docs/dist/doc/README-199.html

org.eclipse.jdt:ecj 3.27.0+ requires Java 11

com.google.errorprone:error_prone_core 2.9.0+ requires Java 11
@olamy
Copy link
Member

olamy commented Apr 10, 2023

-1
it just downgrade dependencies to very old versions (and maybe with some security issues).
we are in 2023.
https://endoflife.date/java
and BTW eclipse ecj or errorprone users are aware of this.

@slachiewicz
Copy link
Member Author

slachiewicz commented Apr 11, 2023

This is to fix #247 where we upgraded Java for part of artefacts in patch versions.
My goal is to restore compatibility, release one version and then upgrade project to Java 11 in next minor version

@olamy
Copy link
Member

olamy commented Apr 11, 2023

This is to fix #237 where we upgraded Java for part of artefacts in patch versions. My goal is to restore compatibility, release one version and then upgrade project to Java 11 in next minor version

it's a test artifact so I do not understand the problem..... the most important compiler (e.g javac) is still compatible with 8 at runtime!
here you are talking about test dependency. I don't really understand what is the problem?
we are still releasing javac compiler which is java 8 compatible at runtime according to those lines

<maven.compiler.source>8</maven.compiler.source>

@slachiewicz
Copy link
Member Author

Sorry #247 from issues

@olamy
Copy link
Member

olamy commented Apr 11, 2023

there is a probably a workaround #247 (comment) instead of downgrading so many dependencies...
because at the end of the day users will need to upgrade..... we can't keep maintaining such old version of java...

@slachiewicz
Copy link
Member Author

As I mentioned above. Goal is to release one that support Java 8 and then release next versions where we explicitly say that we support only Java 11. Difference in few days only.

@olamy
Copy link
Member

olamy commented Apr 11, 2023

As I mentioned above. Goal is to release one that support Java 8 and then release next versions where we explicitly say that we support only Java 11. Difference in few days only.

-1 to this it doesn’t make sense because of the changes to the downstream dependencies (ecj, aspectj, errorprone)....
again there is probably a workaround for this user to try...
if you want to do so. create a release branch 1.12.1.x and work on this with a release 1.12.1.1 (but frankly that's non sense) but do not downgrade master branch it doesn’t make sense....

@slachiewicz
Copy link
Member Author

Thank you for you input.

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.

2 participants