JEP 200: The Modular JDK

[David M. Lloyd]

On 8/5/14, 11:49 AM, mark.reinhold at oracle.com wrote:
> New JEP Candidate: http://openjdk.java.net/jeps/200

A few minor comments:

We've found that when it comes to deciding when to or when not to 
re-export an API dependency of another API module, the criteria comes 
down to whether the importing API makes use of the imported API's types 
directly in its API classes.  If not, then re-exporting is generally 
counter-productive.  By this standard, there may be more re-exporting 
going on than strictly necessary or desirable in this document.

As a matter of principle I'm generally opposed to exporting specific 
module packages only to specific other modules.  I think this indicates 
that a module split is required.  I'm guessing that at the root of this 
problem is an attempt to avoid circular dependencies during compilation, 
but I would rather that issue not be punted to the runtime.


-- 
- DML