Proposal: #ReflectiveAccessToNonExportedTypes: `exports dynamic`

[Sven Reimers]

The point was if you want to limit reflective access to special modules you
would need some kind of alias or token as the target of your export, e.g.
jpa and not hibernate.

If dynamic export is not limited, all is fine - agreed.

Sven
Am 01.07.2016 10:49 schrieb "Sander Mak" <sander.mak at luminis.eu>:

>
> > On 01 Jul 2016, at 10:41, Sven Reimers <sven.reimers at gmail.com> wrote:
> >
> > Hi all,
> >
> > regarding exporting DTO to hibernate..
> >
> > I think the whole point of having JPA is to not have explicit dependency
> to
> > hibernate..
>
> Hence the proposal for `exports dynamic`, where you don't have to qualify
> the export to a certain module. The relation between the DTO module and JPA
> would be expressed by having a `requires jpa` (or whatever module the spec
> annotations will live in). The `dynamic` part makes sure no other modules
> take an accidental dependency on your DTOs (if that's what you want) at
> compile-time. All sounds good to me.
>
>
> Sander
>
>