Lew wrote:
>> Certainly. But the OP was suggesting a tool that scanned the .java
>> file lexically for im****ts, and that would fail to find
>>
>> p1.p2.p3.class1 c = null;
>>
>> Personally, I'd build a dependency tool that scanned the .class file,
>> not the .java file. (If there is no .class file, you don't need to
>> know anything about dependencies to realize that the .java file needs
>> to be recompiled.) The bytecode has everything you need, and there
>> is lots of open-source code out there to help you parse it.
>
> Doesn't every existing tool that does dependency scanning work off
> the .class files?
>
> It escaped me that the question restricted the scan to source files. I
> simply figured any dependency tool would simply have to work off
> the .class files, never even dreaming that anyone would try to do it
> from the source.
There are more things in Heaven and Earth, Horatio, than are dreamt of in
your philosphy. :-)
|
