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

Add "fixJava8Classpath" option to support multirelease projects #171

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kohlschuetter
Copy link

In certain environments that build multirelease jars, the Maven "classes" directory contains class files with newer Java versions, whereas the Java 8 versions are stored elsewhere.

Add a boolean "fixJava8Classpath" option that, once enabled, automatically fixes these classpath entries. It checks for the presence of a sibling directory named "classes-java8". If that's available, then the original classpath entry is replaced.

In certain environments that build multirelease jars, the Maven
"classes" directory contains class files with newer Java versions, whereas
the Java 8 versions are stored elsewhere.

This prevents retrolambda from working, as
java.lang.UnsupportedClassVersionError is thrown.

Add a boolean "fixJava8Classpath" option that, once enabled,
automatically fixes these classpath entries. It checks for the presence
of a sibling directory named "classes-java8". If that's available, then
the original classpath entry is replaced.
@luontola
Copy link
Owner

Requires a test case to reproduce whatever was the issue. "classes-java8" sounds like something project specific.

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