-encoding and -source in module-info.java

[Rémi Forax]

On 01/24/2012 10:47 PM, Eric Johnson wrote:
> Of course, to me, this circles back to the point I've chimed in on 
> with others before. Module info shouldn't be in a file ending in 
> .java. It *isn't* part of the language, it is part of the metadata for 
> using the language.
>
> -Eric.

There is no need to put compilation options in the module description file,
defining a module and compiling sources are two different tasks,
the module metadata describe requires/provides of a module that it.
Why do you want mix these to things together ?

I believe that Maven has the two things mixed only because there is
no module description in Java. When Java 8 will be out, it will be more 
clear,

Rémi

>
> On 1/24/12 10:35 PM, Neal Gafter wrote:
>> The idea of using module-info.java to specify compilation options seems
>> most tempting, but as long as it is a source file in the language, it 
>> must
>> be subject to those options as well.  Which means that specifying them
>> inside the file itself is pretty pointless.  As to the source level, 
>> what
>> can the language specification say other than that "8" is the only 
>> allowed
>> value?  And what can the next version of the language specification say
>> other than that "9" is the only allowed value?