Skip to content

Conversation

csware
Copy link
Contributor

@csware csware commented Jan 23, 2024

For the compiler --release check to work, we need a more recent maven-compiler-plugin version (at least 3.6).

relates to issue #301

@csware csware changed the title Update the maven-compiler-plugin Update the maven-compiler-plugin to make the --release check work Jan 23, 2024
<artifactId>maven-compiler-plugin</artifactId>
<version>3.3</version>
<configuration>
<source>9</source>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

already set as properties above

For the compiler --release check to work, we need a more recent maven-compiler-plugin version (at least 3.6).

Signed-off-by: Sven Strickroth <email@cs-ware.de>
@csware
Copy link
Contributor Author

csware commented Feb 2, 2024

ATM JDK10 is required.

I already have a branch that unbreaks JDK9 and unbreaks JDK8, cf. #301 (comment) and #301 (comment)

I can open a PR as soon as PR #302 and PR #313 have been decided (becasue it will conflict with these changes)

@csware
Copy link
Contributor Author

csware commented Feb 2, 2024

Maybe we should raise to JDK10 in pom.xml until we have fixes for JDK9...

@mikesamuel
Copy link
Contributor

Ugh. JDK 9 is the new JDK 6.

@csware csware closed this Feb 2, 2024
@csware
Copy link
Contributor Author

csware commented Feb 2, 2024

Closed in favor of PR #321

@csware csware deleted the release-check branch February 2, 2024 19:42
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