Is there really a jdk.proxy1 module?

Stephane Epardaud stef at
Tue Dec 8 14:59:26 UTC 2015

Actually no, I've found that insted of accessing the proxy class
directly I should just access the proxied annotation class and it works.

Thanks anyway.

Except now I have to add a read to scan annotations of another module,
which naturally introduces a cycle. This can't be right. Suppose I've a
Framework module "F" and an app "A" which reads "F" (since it works for
that framework). Now when that framework scans annotations in "A" it
can't use reflection to access them because it doesn't read "A"?

Funny thing is I can add the read and it doesn't complain about cycles,
not sure why.

More information about the jigsaw-dev mailing list