Managing JAR Dependencies

Developing infrastructural components is sometimes difficult when it comes to re-factoring that code—Is that class being used by any other project in your company? How do you determine whether it is? If you’re in luck, your company has a local Maven Repository so you can find out which other projects depend on your artifacts. But that is only half the battle: Which classes do in fact specifically depend on your code?

I recently found a nice tool that solves the problem:

The Class Dependency Analyzer!

Simply add the JAR files to a new work set. After analyzing the classes, the answer is just a Right Click of the mouse away:

Class Dependency Analyzer Screenshot (Small)
Class Dependency Analyzer Screenshot (Small)

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s