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

Do not try to translate classes in META-INF/versions #169

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

Conversation

kohlschuetter
Copy link

In a multirelease-jar environment, there could be classes under META-INF/versions, which retrolambda would try to translate.

As per definition, these are Java classes newer than Java 1.8, so they shouldn't be processed at all, especially since it is expected that there is at least some version (hopefully 1.8 or older) of that class in the path that is not prefixed by META-INF/versions.

Extend FilteringFileVisitor to never visit /META-INF/versions, and modify FilteringFileVisitor so it's usable in all cases, even when no other filtering is required.

In a multirelease-jar environment, there could be classes under
META-INF/versions, which retrolambda would try to translate.

As per definition, these are Java classes newer than Java 1.8, so they
shouldn't be processed at all, especially since it is expected that
there is at least some version (hopefully 1.8 or older) of that class in
the path that is not prefixed by META-INF/versions.

Extend FilteringFileVisitor to never visit /META-INF/versions, and
modify FilteringFileVisitor so it's usable in all cases, even when no
other filtering is required.
@luontola
Copy link
Owner

Requires a test case to reproduce whatever was the issue.

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