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.

JME 3.5.0-alpha1 incompatible with Java 7

See original GitHub issue

The distributed file “jme3-core-3.5.0-alpha1.module” at MavenCentral contains the following:

"attributes": {
        "org.gradle.category": "library",
        "org.gradle.dependency.bundling": "external",
        "org.gradle.jvm.version": 8,

Since it specifies JVM version 8, newer build tools won’t allow it to be used in projects that specify compatibility with Java 7.

This issue arose from 2 changes to “common.gradle”:

Jdk 11 compatibility (ad2ba95e993d3ad16f95c189e25c1b2c54763826) which bumped sourceCompatibility from ‘1.7’ to ‘1.8’ and
Gradle 6.9 (PR #1588) which caused Gradle to publish a .module file to MavenCentral

Returning to 1.7 compatibility will require some changes to our source code, to avoid using Java 8 features such as lambdas.

Issue Analytics

State:
Created 2 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

2reactions

Ali-RScommented, Nov 19, 2021

I remember hearing we needed Java 7 compatibility to run on Android devices

Not anymore. We can use new language features (excluding sealed class) up to Java 17 (including lambda, records, text block, instanceof pattern matching, switch expressions) on old Android versions as well (Android 4.4+) using Android desugaring. I have already tried it.

Note that my above statement is only regarding Java Language features.

New Java API features such as Java 11 HttpClient and Java 17 Foreign Function & Memory API is not supported by Android yet.

1reaction

stephengoldcommented, Nov 19, 2021

I see you took care of that for me. Thanks!

https://hub.jmonkeyengine.org/t/jme3-minimum-java-version/45111