Static imports might help you:
import static my.package.MyClass.myMethod;
However, using even normal imports for dependency documentation is
flaky, as you can always fully qualify the name.
If you use minimal interfaces (as opposed to humane interfaces) then
importing the interface type is enough to see the dependencies, really.
VisionSet - 17 Dec 2005 14:29 GMT
> Static imports might help you:
>
> import static my.package.MyClass.myMethod;
ahh yes, thanks
> However, using even normal imports for dependency documentation is
> flaky, as you can always fully qualify the name.
>
> If you use minimal interfaces (as opposed to humane interfaces) then
> importing the interface type is enough to see the dependencies, really.
Yes but as an intermediate/during refactoring to that stage, the above
suggestion will be useful.
--
Mike W