-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
JDK-8283730: Improve discussion of modeling of packages and modules #7980
Closed
+94
−15
Closed
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
f9bc1f8
JDK-8283730: Improve discussion of modeling of packages and modules
jddarcy 1e7e774
Add links and fix typos.
jddarcy e26cff7
Fix more typos.
jddarcy 640d6e8
Update package-info file.
jddarcy 8892922
Various edits.
jddarcy 109227d
Respond to review feedback.
jddarcy a5a2142
Merge branch 'master' into JDK-8283730
jddarcy 4652121
Add discussion of automatic modules.
jddarcy c146bbc
Further refine discussion of ModuleElement.
jddarcy d1d9d8c
Merge branch 'master' into JDK-8283730
jddarcy d83c69d
Respond to review feedback.
jddarcy bc93fe1
Refine package description.
jddarcy a294451
Respond to more review feedback.
jddarcy 63404c7
Merge branch 'master' into JDK-8283730
jddarcy 08aaeec
Reflow paragraphs.
jddarcy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
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.
The
Filer
references here feel a bit weird. While mostTypeElement
s presumably have an explicit backing construct (i.e. a file), I suspect that only minority of the backing constructs are created using aFiler
, but the text suggests(?) that allTypeElement
s with a backing construct are created viaFiler
.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.
In the latest pushed, pulled out the information specific to an annotation processing. New plain text:
ModuleElement:
"The represented module may have an explicit reference representation (either source code or executable output) or may be created from implicit information. The explicit and standalone source code construct for a module is typically a module-info.java file (JLS 7.7). Automatic modules (JLS 7.7.1) are named modules that do not have a module-info file. Implicit information is used to model unnamed modules.
In the context of annotation processing, a module element can be:
PackageElement
The represented package may have an explicit reference representation (either source code or executable output) or may be created from implicit information. The explicit and standalone source code construct for a package is typically a package-info.java file (JLS 7.4.1). Implicit information is used to model unnamed packages.
In the context of annotation processing, a package element can be:
TypeElement
The represented class or interface may have a reference representation (either source code or executable output). Multiple classes and interfaces can share the same reference representation backing construct. For example, multiple classes and interface can be declared in the same source file, including, but are not limited to:
In the context of annotation processing, a type element can be: