Trace class dependency at compiletime

Hi!

I am experiencing an irritating problem - some packages are automatically compiled that I haven't specified, of course because something that I am compiling references these other packages.

The package i am compiling (using ant) is meant for a plugin 1.3 enabled browser and some of my other packages contain 1.5 specific code (generics). I am therefore trying to compile the client packages with the -source 1.3 flag to the compiler but it breaks on the 1.5 specific code. Now to my problem: I can't find the code that is referencing the 1.5 packages!

Is there a way to trace the depencies at compile-time? (So that I can step backwards in that trace to see which source is doing the referencing of the unwanted packages)

Best regards,

Marcus

[786 byte] By [M_Hjortzena] at [2007-10-1 22:36:20]