As stated in all the other answers: No. The package hierarchy means nothing outside of the mind of the person who set it up.
In my opinion this is Java's major flaw. When building up monster systems by merging together other monster programs, nothing beats Java-the-language. All other languages eventually end up in confused, undocumentable, indecipherable piles of code.
Well, so does Java, but it gets a lot further than any other language I've used. But its ignorance of package hierarchy--the inability to encapsulate data in a package hierarchy--is the limitation, or brick wall, that stops it. I can put a system, or set of classes that work together, in a single package. Then I can make a bunch of those classes package private so that when this package is added to another super-system that super-system cannot see--and be confused by--those hidden classes.
But if my system is already super enough ("super" as in "superman", not "superclass") to need several packages for clarity, my formerly package-private classes must now be public, and I can't stop the super-super-system from seeing everything in my super-system.
To make a vast, complex system work, the complexity at every point must be minimized. My super-system has to look as simple as possible to the super-super-system I'm adding it to. Having all the pipes and wires and beams and welds sitting out in public display because I cannot make them package-level-private does not help this.
I hope Jigsaw, mentioned elsewhere, will help. I also hope developer tools such as IDEs will start displaying packages in an outline format rather than treating a.b and a.b.c.d.e as if they were all on the same level--just elements in the same list.