Skip to content
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

Is there any plan to have Java 17 support? #605

Open
a1shadows opened this issue Nov 9, 2023 · 4 comments
Open

Is there any plan to have Java 17 support? #605

a1shadows opened this issue Nov 9, 2023 · 4 comments

Comments

@a1shadows
Copy link
Collaborator

Currently, the helloworld project does not build successfully on mvn clean install with java 17. I tried writing a few custom tests which don't seem to work.

Is there any plan/mandate to update dependencies so that project runs successfully on java 17 to which we can contribute?

@baulea
Copy link
Contributor

baulea commented Nov 11, 2023

I would like to contribute, too.

@infoShare
Copy link

Hello,

we're using zerocode on our project with java 17 with no issues (except additional --add-opens args for compilation)
Here you can find some snippet:
https://github.com/infoShare/zerocode-example

@a1shadows
Copy link
Collaborator Author

Thank you

Hello,

we're using zerocode on our project with java 17 with no issues (except additional --add-opens args for compilation) Here you can find some snippet: https://github.com/infoShare/zerocode-example

Thanks, we'll try and use this. But shouldn't we not have to override warnings to get the code to run? I think eventually the deprecated libraries currently used will have to be upgraded. If that is a direction that we want to look into, I would love to contribute. We plan to use Zerocode long term in our org.
@authorjapps can you comment?

@authorjapps
Copy link
Owner

I think eventually the deprecated libraries currently used will have to be upgraded.

@a1shadows , I think 1st step is to upgrade the libraries to latest and make it runnable in Java8.

		|(1)------------> java8 releases (existing java8 users)
		|
(currently)------

Then, we need to fork it out to a separate path for java17 release.

		|(1)------------> java8 releases (existing java8 users)
		|
(next)-----------
		|
		|(2)-----------> java17 release (users with java17 sdk)

I will raise raise a milestone for this soon, with tickets for 1st steps and next steps.

Please vote if it sounds correct.

@authorjapps authorjapps added this to the JAVA17-AMERICA milestone Nov 22, 2023
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

No branches or pull requests

4 participants