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
8259039: Passing different version to --release flag than javac version output warning #5053
Conversation
…on output warning
|
@lahodaj This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
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.
Nice work
@lahodaj This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 466 new 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 this automatic rebasing, please check the documentation for the /integrate command for further details.
|
/integrate |
Going to push as commit 699865f.
Your commit was automatically rebased without conflicts. |
For code like:
certain combination of command line options produce a proprietary warnings:
But some do not:
The reason is that the
ct.properties
files does not markcom.sun.nio.file
as proprietary. The proposed fix has two parts:-adds
proprietary
to thecom.sun.nio.file
package inct.properties
-limits the
ct.properties
so that it is only used for-source 8
. Thect.properties
contains 3 types of information: it hides some packages, it marks some packages as "proprietary" (so that they produce the warning), and assigns packages to compact profiles. For-source 9+
, most of these is not needed - packages are hidden using the module system, the only packages that need a warning are from thejdk.unsupported
module, and there are no compact profiles. So for-source 9+
, we don't need to use thect.properties
. (Note none of this applies to--release
- it uses a different database.)Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5053/head:pull/5053
$ git checkout pull/5053
Update a local copy of the PR:
$ git checkout pull/5053
$ git pull https://git.openjdk.java.net/jdk pull/5053/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5053
View PR using the GUI difftool:
$ git pr show -t 5053
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5053.diff