Lack of "export dynamic" requires to export everything for existing frameworks

I believe it would be better to introduce a concept of "privileged module" instead of introducing "weak module" concept. "privileged module" can reflect on any unexported (and exported) type of other resolved modules of a layer that it belongs to. In addition, we can introduce command line flags

Re: Lack of "export dynamic" requires to export everything for existing frameworks

On 03 Oct 2016, at 13:30, Peter Levart > wrote: Use qualified exports? Which circles back to the discussion that you don't necessarily know at compile-time which JPA/DI/whatever implementation you're targeting with the module in a Java EE

Re: Lack of "export dynamic" requires to export everything for existing frameworks

Hi Paul, On 10/03/2016 11:23 AM, Paul Bakker wrote: I have updated the migration demo that Sander and I showed at JavaOne to the latest Jigsaw prototype ( https://github.com/sandermak/java9-migration-demos). This is a Spring/Hibernate application. The goal is to migrate the app's code to a

Lack of "export dynamic" requires to export everything for existing frameworks

I have updated the migration demo that Sander and I showed at JavaOne to the latest Jigsaw prototype ( https://github.com/sandermak/java9-migration-demos). This is a Spring/Hibernate application. The goal is to migrate the app's code to a named module, while keeping libraries as automatic modules