Re: Way to bypass "uniquely visible" check for named vs. unnamed module conflict?

2018-12-20 Thread Jonathan Gibbons
Bug filed: https://bugs.openjdk.java.net/browse/JDK-8215739 -- Jon On 12/20/2018 11:46 AM, Alex Buckley wrote: Thank you Stephan. We're looking into javac now. (BTW I enjoyed your comment on SO that "Adding module-info.java is not part of the problem, but part of the solution (thereby

Re: Way to bypass "uniquely visible" check for named vs. unnamed module conflict?

2018-12-20 Thread Alex Buckley
Thank you Stephan. We're looking into javac now. (BTW I enjoyed your comment on SO that "Adding module-info.java is not part of the problem, but part of the solution (thereby moving your code from classpath to modulepath)".) Alex On 12/20/2018 5:21 AM, Stephan Herrmann wrote: Sorry, if

Re: Way to bypass "uniquely visible" check for named vs. unnamed module conflict?

2018-12-20 Thread Stephan Herrmann
Sorry, if that part was left implicit. Yes, all versions of javac that I tried accept all four invocations. This includes the following builds: - 9.0.4+11 - 10.0.1+10 - 11.0.1+13-LTS - 12-ea+19 Stephan On 20.12.18 00:05, Alex Buckley wrote: I'm seeing multiple claims in the SO item and the