Closed
Description
I was also looking for an option to detect any access to a "forbidden" package
or package structure, as in:
@defaultMessage Hands off from these packages.
com.foo.**
com.boo.**
The use case scenario is actually quite specific -- we have a project structure
which is shaded/ obfuscated during the build, but during development all
packages are visible. It'd be nice to capture those forbidden package calls
even before obfuscation/ ITs take place.
Should be trivial to implement -- you don't need to even know what is in those
packages, just scan all class literals.
Parsing and distinguishing these rules from other rules may require changes in
ruleset syntax though.
Original issue reported on code.google.com by [email protected] on 4 Nov 2014 at 11:32