JDeps: detecting offending packages
rfscholte at apache.org
Sun Nov 15 17:49:42 UTC 2015
Ah, I see. Adding usage of java.awt.peer.ComponentPeer did indeed expose
an offending package again.
Just out of interest: will jdeps only detect violations of JDK internal
APIs or will it also detect violations on modules? In case I switch from
executable jar to executable module it could happen that it breaks due to
usage of non-exported packages, right?
Op Sat, 14 Nov 2015 17:29:58 +0100 schreef Alan Bateman
<Alan.Bateman at oracle.com>:
> On 14/11/2015 16:05, Mandy Chung wrote:
>> I think jdeps should continue to flag the critical JDK internal APIs
>> listed in JEP 260 but they are accessible at runtime. I file a bug:
> I agree and I expect it will be straight-forward once they are moved to
> their own module.
More information about the jigsaw-dev