Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

maven.compiler.source & maven.compiler.target 8

See original GitHub issue

These two properties are defined in root pom.xml, but shouldn’t both be set to 11? Furthermore, maven.compiler.release should be used instead, which also makes sure that you don’t use JDK 12+ APIs.

Issue Analytics

State:
Created 3 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

ppalagacommented, Jan 15, 2021

it’s always a bit frustrating if you think you’re done (locally), just to see CI failing after the push

I’d find it more frustrating to have slow local build 😃

0reactions

famodcommented, Jan 17, 2021

I’ve given up on this for now:

release doesn’t work in client due to:

[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] exporting a package from system module java.base is not allowed with --release
[INFO] 1 error

<release>8</release> doesn’t work in daemon due to:
```
package sun.misc does not exist
```
See also: https://stackoverflow.com/a/60172333/9529981 (which suggest adding an export, which would yield the same problem as in client) Maybe I’m wrong, but this smells like a toolchain and/or mutli-release jar problem.
sniffer signatures only go as far as 1.8