Jaikiran,
This issue is on our radar; there is no need for any additional action
on your part at this point.
-- Jon
On 9/14/18 7:50 PM, Jaikiran Pai wrote:
Hello Peter,
On 14/09/18 1:03 PM, Peter Levart wrote:
The check for main class is performed after compilation (which
actually produces the main class name).
I think it would be possible to check for all classes compiled from
the source file after compilation without to much complication. The
compilation produces classes and stores them into a Map<String,
byte[]>. The keySet() of that map is a Set of compiled class names.
Each of them could be tested via .getResource() invoked upon the
application class loader. The error could even point to the URL of the
conflicting class file that way...
Thank you for moving this to the correct mailing list. Thanks for those
details about how it's done and what can be done to improve this. Should
I report this as an enhancement request at bugs.java.com? I don't have
access to the OpenJDK JIRA for creating this request there.
-Jaikiran
