Alan.Bateman at oracle.com
Thu Dec 15 05:31:20 PST 2011
On 15/12/2011 13:08, David Bosschaert wrote:
> I still strongly believe that the it's not right to define module
> metadata in Java source files and have it end up in compiled .class
> files inside jars. I thought that this decision was going to be made
> by the modularity JSR so I am worried that the changes like this start
> appearing in the VM and language design itself without having
> consulted the JSR about it.
I don't know if you've seen the requirements document (which I believe
will be a starting point for the JSR) but it captures the divergent
opinions on this topic:
> To me it seems ilke the use of XML would be a good way to represent
> module metadata. Its highly extensible (you can add custom-namespaced
> tags anywhere), and quite readable but both humans and machines.
One thing to mention is that with the platform modularization then it's
possible that there will not be XML support in the base module (and the
module system needs to work with just the base module installed, say in
footprint constrained embedded environment for example).
More information about the jigsaw-dev