From: SourceForge.net <no...@so...> - 2006-11-30 19:12:37
|
Bugs item #1604465, was opened at 2006-11-28 07:18 Message generated for change (Comment added) made by hansonr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=1604465&group_id=23629 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Packaging Group: v10.9 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nicolas (nicove) Summary: Jmol conflicts with CDK, Obrador, etc. Initial Comment: Jmol.jar includes particluar versions of com.obrador. cdk.jar includes particluar versions of Jmol, etc. This makes it impossible to develop applications which need functionalities from several packages! Reason: Assume you want to use "structgen" from "cdk", latest version, and something else from the latest Jmol in an application. Fact is that jmol.jar and cdk.jar come with non-latest versions of other packages included. So, in you new application you need to specify the latest cdk.jar, and jmol.jar to the JVM. However, cdk.jar includes and older version of jmol, and jmol includes another version e.g. of com.obrador. Depending of the Java package lookup sequence, you will encounter compilation and/or execution problems, because several incompatible versions are present, and it is practically not manageable to provide the right version for the right application. The only solution would be: When Jmol e.g. needs a particular version of com.obrador and wants to include this library in its jar file, them the package must be renamed there, e.g. com.obradorXXX. If cdk wants to include a particular Jmol version in its jar file, the the jmol packages must be renamed there e.g. to JmolYYY. Submitted by: Bru...@br... ---------------------------------------------------------------------- >Comment By: Bob Hanson (hansonr) Date: 2006-11-30 13:12 Message: Logged In: YES user_id=1082841 Originator: NO This is certainly a concern. If you can identify exactly what is needed in Jmol for your specific needs, that might help. Certainly, for example, if we need to update the com.obrador version, we should do that. Other than that, the simple solution I suppose is for you to do minor changes such as this on your own within the Eclipse environment and put the pieces together as you need to. I realize that's not an ideal solution. ---------------------------------------------------------------------- Comment By: Nicolas (nicove) Date: 2006-11-28 07:42 Message: Logged In: YES user_id=1096197 Originator: NO My 2 cts ... Renaming a package is not really a clean option: that would mean modifying the source code of the package also. Would a Jmol.jar with no dependencies included be suitable for your need ? Nico ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=1604465&group_id=23629 |