RFR: 8236842: Surprising 'multiple elements' behaviour from getTypeElement when cross-compiling with --release [v2]

[Jan Lahoda]

> Unqualified Elements.getTypeElement(CharSequence) and Elements.getPackageElement(CharSequence) search for elements
> across all modules in the module graph, and only return a value when they find exactly one element. This is
> troublesome, as an element (uniquely) visible from a root module may be "hidden" by an element that is not visible from
> any root module (i.e. is internal to some module that is not in the root module set). The idea proposed here is that
> these unqualified methods would first look for elements visible from the root modules, and would search the internals
> of other modules only if nothing would be found in the first round.  The draft of the corresponding CSR is here:
> https://bugs.openjdk.java.net/browse/JDK-8253168.

Jan Lahoda has updated the pull request incrementally with one additional commit since the last revision:

  Reflecting review comments - improving javadoc, avoid repeated search of modules that have already been searched.

-------------

Changes:
  - all: https://git.openjdk.java.net/jdk/pull/200/files
  - new: https://git.openjdk.java.net/jdk/pull/200/files/f685a41b..3eb2c0bd

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jdk&pr=200&range=01
 - incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=200&range=00-01

  Stats: 36 lines in 2 files changed: 22 ins; 0 del; 14 mod
  Patch: https://git.openjdk.java.net/jdk/pull/200.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/200/head:pull/200

PR: https://git.openjdk.java.net/jdk/pull/200