John Schretz wrote:
Bear Bibeault wrote:No. It seems like a waste of time to me. Just dump all the jars into the lib during the automated build and who cares if they're structured or not.
I do agree, i guess its more for my sanity. I have a habit of trying out new jars, then choosing to not use them and leaving them behind. Wouldn't want to bloat the app with jars not being used.
For now i just created a text file with a list of jars that belong to each other and what they are used for. Only thing is I have to now maintain it. I was able to at leas get rid of old jars when i created the list.
So, you are having managing the jars that are the dependencies of the jars that you use?
It might help if you use
maven as your build tool. In maven, you specify only the jars that you are dependent on. It automatically finds out the dependencies' dependencies and downloads them. That way, once you stop using a lib, just remove it from your build file, and it will automatically stop using it (and it's dependencies).