-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8341342: Elements.getAllModuleElements() does not work properly before JavacTask.analyze() #26694
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
base: master
Are you sure you want to change the base?
Conversation
…e JavacTask.analyze()
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
@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 42 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. ➡️ To integrate this PR with the above commit message to the |
Webrevs
|
@Test | ||
public void automaticallyEnter() { | ||
//make sure the get{All,}{Module,Package,Type}Element{s,} methods will automatically enter: | ||
List<Consumer<JavacTask>> testCases = List.of( |
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.
You can use @ParameterizedTest @MethodSource("taskFactory")
for each test case, and static JavacTask taskFactory() { /* ... */}
for junit to call to create the task argument for each test.
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.
lgtm
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.
Thanks. This test is indeed a bit hard to organize due to being stateful. We can reorganize it if we need later.
When calling
Elements.getTypeElement(...)
orElements.getPackageElement(...)
, javac itself ensures that the enter phase is already done. That is, sadly, not done forElements.getAllModuleElements()
. This PR fixes that.See:
https://github.com/openjdk/jdk/pull/18934/files#r1767657515
for a practical case.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26694/head:pull/26694
$ git checkout pull/26694
Update a local copy of the PR:
$ git checkout pull/26694
$ git pull https://git.openjdk.org/jdk.git pull/26694/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26694
View PR using the GUI difftool:
$ git pr show -t 26694
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26694.diff
Using Webrev
Link to Webrev Comment