"Clark, Stacie" wrote:
>
> If you are allowed to, you could always factor out the dependency into a
> third class that handles the relationship between the two classes. Cross
> class dependencies generally (but do not always) indicate that some
> refactoring needs to be done.
Hello,
BTW: I would like to use a tool which gives me a list of all
cross _package_ dependencies in my project.
It would be usefull because a cross class dependency within
one package is not so bad, but across packages it is really
unnice.
Unfortunately I didnt found such a tool anywhere ?
thanks
mfg Frank Endriss
