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

[Build] Set Java Compiler's -release option instead of -source + -target #214

Merged
merged 1 commit into from
Oct 28, 2024

Conversation

HannesWell
Copy link
Contributor

Using the --release option instead --source plus --target is more convenient (just one option) and more powerful (checks also that now newer Java API is used even if the executing JDK is newer).

Copy link
Member

@NiklasRentzCAU NiklasRentzCAU left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did not know about this option yet, thanks.
However, the maven-javadoc-plugin version is intentionally set to Java 8, as a newer version causes the Javadoc plugin to fail, and as I recall in a spectacular way that I was not inclined to fix. Therefore this should be left at Java 8 as it still works as intended and, most importantly, makes publishing via ossrh possible.

@HannesWell
Copy link
Contributor Author

Therefore this should be left at Java 8 as it still works as intended and, most importantly, makes publishing via ossrh possible.

Sure JavaDoc generation should of course work.

Kept it as it is at 8.

Using the --release option instead --source plus --target is more
convenient (just one option) and more powerful (checks also that now
newer Java API is used even if the executing JDK is newer).
Copy link
Member

@NiklasRentzCAU NiklasRentzCAU left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alright, thanks!

@NiklasRentzCAU NiklasRentzCAU merged commit e98296d into kieler:master Oct 28, 2024
2 checks passed
@NiklasRentzCAU
Copy link
Member

See #220, something went wrong with this PR after all.

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.

3 participants