Runnable JAR with duplicate dependencies?

If the major version number changes it means that backwards compatibility may have changed.

If the major version number changes it means that backwards compatibility may have changed. You could try with the latest version and hope that they just did add methods and that the old way of working, but even if NoSuchMethod exception is not thrown there is no guarantee (maybe with the new API you should call differente methods to get the same results). I would contact the provider of the library and ask them if compatibility is broken.

If they do not answer or it is broken, and you have the source code, the only possibility would be refactoring one of the libraries (probably 1.0); v.g. Putting all of it in new packet v1. Then you would have to change the project that depends of it.

If none of the above works, then the solution would be an OSGi container or to setup project A and project B as two different executables and setup project B as a server that answer project A messages. Messy.

Thanks. Just as a side note, lib-1.0 and lib-2.0 aren't the actual libraries; they are just examples. The major and minor version numbers have no significance in my case, but could be the case for others.

– E-rich Aug 19 '11 at 14:13 If the difference is in minor version number, then just by using the last number you should be safe (if the provider of the library did things as it should). If the difference was with a release number, usually it should not really matter which one you used (but the last one would be advised). – SJuan76 Aug 19 '11 at 14:28 I ended up just updating my project A to use the lib-2.0 library.It did require me to refactor some of my code, but luckily it wasn't much.

Luckily the changes I had to make were small, but if they were going to take up more time I probably would have looked more into OSGi. Thanks for your help! – E-rich Aug 22 '11 at 15:41.

The fix is to only include one version of the library which can satisfy both of the libraries that use it. If that's not possible, you'll have to find a different way of going about things such that you can eliminate the conflict. Options include: Remove one or more of the uses from your code that are causing the NoSuchMethodError.

Modify the source of one or more of the libraries so they can happily coexist. Use an OSGi container, which would allow you to have two versions of the same library in the same application.

As SJuan stated, you could use OSGI to set it up correctly. en.wikipedia.org/wiki/Java_Classloader#J....

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.