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
8295176: some langtools test pollutes source tree #10724
Conversation
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
Webrevs
|
Thanks so much for fixing this. It was beginning to irritate me. The fix is ok, but doing a bit of archaeology, it looks like the fix for JDK-8173605 introduced the problem. JDK-8173605 attempts to remove support for source and target 1.7 option in javac. In so doing, the test ReleaseOption.java In particular the Summary line in ReleaseOption.java is stale. It is not clear to me that the test serves any real purpose - compiled directly or through the API. |
I confirm that the proposed fix solves the problem. I suggest a push either after
Looks good to me. |
@lahodaj This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. 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 8 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
The proposed change restoring the negative nature of the test is better than my suggestions. Thanks, Look good to me. |
Thanks for the reviews! |
/integrate |
Going to push as commit 71aa821.
Your commit was automatically rebased without conflicts. |
The
ReleaseOptionThroughAPI.java
test compiles another test source,ReleaseOption.java
. But it does not specify the output directory, so javac generates the classfile next to the source files into the source directory, causing trouble.The proposed fix is to add
-d .
to the test, so that the classfile is not generated into the working directory.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10724/head:pull/10724
$ git checkout pull/10724
Update a local copy of the PR:
$ git checkout pull/10724
$ git pull https://git.openjdk.org/jdk pull/10724/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10724
View PR using the GUI difftool:
$ git pr show -t 10724
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10724.diff