understanding permission access using packages
Posted on 2004-09-08
I recently organized my application into seperate packages and directories.
the top level file containing main imported all of these packages i.e.
where mypackage contained numerous related classes
I had a long permission changing and explicit import debugging process before i was
able to get everything to compile again under this new organization
what I didn't understand was why many of the classes in the package,
which I was attempting to access in a nested class in the main file needed to be
imported explicitly before the compiler would find it.
why didn't the import mypackage.*; find all of them?
is that by design or is it probably something I did wrong?
I had to explicitly import about 20 classes of the package