The ability to find unused methods and fields is good (I really liked the idea below about highlighting deprecated methods too) ..but also it'd be extremely useful to extend this functionality upwards to help find unused classes and even packages.
I often get codedrops from third parties that need quite heavy refactoring in the early stages.. this is why Idea is such a godsend.. only too often this code is full of orphaned classes and renamed packages and all manner of junk that wastes so much time struggling to understand and wasteful on resources, how many times have I wasted refactoring classes I later find aren't being used, and were moved to some other package.. sigh! - why can't everybody just use Idea?? Anyway I can use tools like JDepend or SmallWorlds to help me track dependencies and impact but I haven't been able to find anything that will do the reverse, find the junk that needs deleting or serious re-design. My best attempt at doing this for a large project involves compiling the source, using a dependency-aware Jar utility to create a jar from the main class, unpacking this jar to a temp dir and do a visual diff on the build classes and the jars classes.. pretty awkward and things get complicated the more entry-points a project has (psvm unit tests don't help matters). Basically I was wondering if they'res any plans to extend "Inspect Code" this way.. or would this make for an interesting plugin project? Richard _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
