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

Plugin now require Java 11 instead of Java 8 #45

Closed
kelheor opened this issue Dec 2, 2018 · 6 comments
Closed

Plugin now require Java 11 instead of Java 8 #45

kelheor opened this issue Dec 2, 2018 · 6 comments

Comments

@kelheor
Copy link

kelheor commented Dec 2, 2018

Were there any serious reasons to change Java version from 8 to 11, when Web3j 4 originally supports Java 8?
Now if I want to use your plugin, I have to move from Java 8 to 11, which can potentially cause a lot of issues.
Maybe you can revert it back to 8?

@kelheor
Copy link
Author

kelheor commented Dec 2, 2018

Nevermind. I will update my project to Java 11, maybe it will be better in perspective.

@kelheor kelheor closed this as completed Dec 2, 2018
@ghareeb-falazi
Copy link

We use the plugin for a large project that uses Java 8. Moving to Java 11 is not an option for us at all due to other dependencies. I am in favor of reverting back to 8.

@fcorneli
Copy link

Could someone release a version of web3j-maven-plugin that still supports Java 8?
There is absolutely no reason to jump to Java 11.
Besides, most Java EE runtimes are still on Java 8...

@h2mch
Copy link
Contributor

h2mch commented Jan 10, 2019

after more votes/commets for java8, a new version with java 8 is released. includs also newest web3j core version:

https://github.com/web3j/web3j-maven-plugin/releases/tag/web3j-maven-plugin-4.1.0

@fcorneli
Copy link

@h2mch thanks for the release!

@fcorneli
Copy link

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