Skip to content

Set source and target in jdk9+ profile - #569

Closed
ctubbsii wants to merge 1 commit into
apache:masterfrom
ctubbsii:retain-legacy-compiler-props
Closed

ctubbsii wants to merge 1 commit into
apache:masterfrom
ctubbsii:retain-legacy-compiler-props

Conversation

@ctubbsii

Copy link
Copy Markdown
Member

Use javaVersion to set maven.compiler.source and maven.compiler.target, in addition to maven.compiler.release in the jdk9+ profile, because some plugins still use these properties, even when maven.compiler.release is set. So, it is still useful to have these set automatically by the single property, javaVersion.

Use `javaVersion` to set `maven.compiler.source` and
`maven.compiler.target`, in addition to `maven.compiler.release` in the
`jdk9+` profile, because some plugins still use these properties, even
when `maven.compiler.release` is set. So, it is still useful to have
these set automatically by the single property, `javaVersion`.
@slawekjaranowski

Copy link
Copy Markdown
Member

because some plugins still use these properties, ...

which plugins needs it?

@ctubbsii

Copy link
Copy Markdown
Member Author

because some plugins still use these properties, ...

which plugins needs it?

The main one that affected me was net.revelc.code.formatter:formatter-maven-plugin, but I'm certain there are others out there.

@ctubbsii

Copy link
Copy Markdown
Member Author

I'm going to close this PR, since I no longer think it's worth doing.

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