#112 Handle multiple top-level package names in import-control

Unstable_(example)
wont-fix
Oliver Burn
None
5
2014-02-09
2005-11-25
Darrell DeBoer
No

Our source tree consists of some packages net.foo. and
others com.foo.
, and we wanted to use the new import
control check to control imports between these packages
as well as on other packages.

The current import-control check assumes a single
top-level package in <import-control pkg="foo"/>. We
have modified the check to be configured like:

<import-control>
   <package name="com.foo">
     ...
   </package>
   <package name="net.foo">
     ...
   </package>
</import-control>

This gives us complete control over imports in our
source tree.

The zip file contains a patch file generated against
CVS on 2005-11-25 and 2 new files serving as testinputs
for the new unit tests.

Hope you find this helpful
ciao
Daz

Discussion

<< < 1 2 (Page 2 of 2)
    • status: open --> closed
     
    • status: closed --> wont-fix
     
<< < 1 2 (Page 2 of 2)