I have inherited an RMI client-server app, which I am extending and
maintaining. Unfortunately, the current build procedure creates a
single jar for the entire app, which then resides both on the client
and the server. This means that when even the smallest tweaks are made
on the client GUI (or server persistance, etc), both places have to be
updated.

I would like to partition the app into 3 jars (client, server and a
shared jar for the classes used in the RMI interface). Is there a tool
that would help me visualize the different class-class dependency and
assist me in finding the cleanest way to perform this split?

Thanks for any help.
Boris