On the other hand: Even if the release options refers to another JDK, then the available/used JDK will still call the method, so it is actually referenced at runtime.

On the other hand: Even if the release options refers to another JDK, then the available/used JDK will still call the method, so it is actually referenced at runtime.

Not sure what you mean. If it is a different method, we can't refer to actual JDK which compiler is using currently, because it may not exist here / changed signature etc. So if it is incompatible / not existing method in the current JDK, it will be not called by current JDK because it is technically not possible. This is the main point of the --release option.

Probably 99% signatures will not depend on JDK version but those would be excluded from search just because some may have changed.

Probably 99% signatures will not depend on JDK version but those would be excluded from search just because some may have changed.

Check ct.sym content. If that would be 99% we would not have so many files there. For user it doesn't matter if it is 1% or 10%, the data we use would be seemingly "randomly" correct or incorrect...

On the other hand: Even if the release options refers to another JDK, then the available/used JDK will still call the method, so it is actually referenced at runtime.

Not sure what you mean. If it is a different method, we can't refer to actual JDK which compiler is using currently, because it may not exist here / changed signature etc. So if it is incompatible / not existing method in the current JDK, it will be not called by current JDK because it is technically not possible. This is the main point of the --release option.

Using --release 17 at compile time ensures that we are calling only those methods that really exist at 17. But the physical JDK (e.g., 23) used during development may have a different implementation of that method, and it has additional methods. Search using the method bodies of the physical JDK rather than the intended target JDK may be off in arbitrary ways.

@stephan-herrmann I have posted a patch which check for --release being set lower than default JRE and a warning is issued on the Java Search page. Let me know if this satisfies what you were looking for and if any tweaks are needed.

@stephan-herrmann I have posted a patch which check for --release being set lower than default JRE and a warning is issued on the Java Search page. Let me know if this satisfies what you were looking for and if any tweaks are needed.

From a first glimpse this looks good. I'll check out the branch to see it in action soonish.