Reusing module name token `*` in -d

[Stephan Herrmann]

On 01/22/2017 02:50 PM, Remi Forax wrote:
> interesting !
>
> It's now a warning that you can exclude with @SuppressWarnings("module"):
>   src/main/java/foo/module-info.java:2: warning: [module] module not found: baz
>   exports foo to baz;
 >                  ^

JLS 9.6.4.5 @SuppressWarnings:
"Compiler vendors should document the warning names they support in conjunction
  with this annotation type. Vendors are encouraged to cooperate to ensure that
  the same names work across multiple compilers."

looking forward to seeing this happen,
Stephan

> Rémi
>
> ----- Mail original -----
>> De: "Robert Scholte" <rfscholte at apache.org>
>> À: jigsaw-dev at openjdk.java.net
>> Envoyé: Samedi 21 Janvier 2017 20:12:37
>> Objet: Re: Reusing module name token `*` in -d
>
>> On Sat, 21 Jan 2017 19:35:28 +0100, Stephan Herrmann
>> <stephan.herrmann at berlin.de> wrote:
>>
>>> On 01/21/2017 06:52 PM, forax at univ-mlv.fr wrote:
>>>> Robert,
>>>> How do you compile these 2 modules with Maven ?
>>>>
>>>> module foo {
>>>>   exports foo to bar;
>>>> }
>>>>
>>>> module bar {
>>>>   requires foo;
>>>> }
>>>>
>>>> when compiling 'foo' javac needs to see if 'bar' exists and when
>>>> compiling 'bar', javac will ask to see 'foo'.
>>>
>>> I don't think so:
>>>
>>> "It is permitted for the to clause of an exports or opens statement to
>>> specify a module which is not observable."
>>> [lang-vm.html 1.1.2 - 2017/1/9]
>>>
>>> I assume this will eventually (when??) become part of JLS, right?
>>>
>>> cheers,
>>> Stephan
>>
>>
>> Confirmed. I've added an integration-test to the maven-compiler-plugin,
>> works as expected. No need for cross reference dependencies.
>>
>> thanks,
>> Robert