This repository has been archived by the owner on Oct 28, 2020. It is now read-only.
Add test showing stricter handling of Symbolic References #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @roscopeco, sorry for never getting back to you, not cool of me. I wondered for a while what to do with this project and now decided that I I won't invest the time into keeping it up to date. I won't renew the domain java9.wtf and won't make any more changes in this project. If you're interested in maintaining it, feel free to create a fork. 🌻 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Java 9 is stricter in how it handles Symbolic References in .class files. While the previous behaviour is strictly a bug according to the spec, it did work, and now it doesn't.