-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8235229: Compilation against a modular, multi-release JAR erroneous with --release #43
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
Conversation
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
@lahodaj The following label will be automatically applied to this pull request: When this pull request is ready to be reviewed, an RFR email will be sent to the corresponding mailing list. If you would like to change these labels, use the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
@lahodaj This change now passes all automated pre-integration checks. In addition to the automated checks, the change must also fulfill all project specific requirements After integration, the commit message will be:
Since the source branch of this PR was last updated there have been 37 commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge ➡️ To integrate this PR with the above commit message to the |
/integrate |
@lahodaj Since your change was applied there have been 37 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 5fef8dd. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
…penjdk#43) * JVM-2031: Prevent PEA materialization takes place in side of a loop * Don't create phi node in MergeProcessor if m and n are same. --------- Co-authored-by: Xin Liu <xxinliu@amazon.com>
A combination of a multi-release modular jar and --release option does not work well, because the appropriate file manager does not have a multi-release option set. The proposal is to set the multi-release option to the file manager.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/43/head:pull/43
$ git checkout pull/43