#167 Re-integration of CDK and JCP application/applet
Following this thread http://www.mail-archive.com/cdk-user@lists.sourceforge.net/msg01619.html , I would like to remind JChemPaint application still relies on a fork of CDK, which is incompatible with CDK releases , available at sf.net / github.
This makes impossible using JChemPaint embedded in applications, that use the sf.net/github CDK releases. Incompatibilites are of various nature, from different CDKConstants to different method signatures. Even if it is possible for certain combination of CDK/JChemPaint versions to be forced to use both CDK versions in a single package, this is prone to errors due to Java class loader having to load different implementation of classes with the same name.
Therefore, it would be highly desirable to avoid JChemPaint relying on a CDK fork and be able to use CDK releases, without additional patches. Ideally, JChemPaint could be configured to use CDK version via some dependency mechanism, without embedding CDK source tree.
That makes sense to me. I will wait for the CDK 1.4 release (which I understand to be coming out soon) and then use that to create a new JCP applet/application release. I'll add info to the JCP download file(s) to indicate what CDK stable version was used. Hopefully that will do.
Mark,
Many thanks - I could confirm there are no more compile troubles when using both JCP and CDK - I've tried successfully JCP 3.1.3 and CDK 1.3.6.
Would it be possible to have additional JCP distribution, which do not embed CDK classes? Otherwise using both JCP and CDK simultaneously on the Java class path results in two copies of the each CDK class .
A quick update: the new renderer API is now part of the 1.4.x branch. The render-basic module is next to be cleaned up and proposed as patch, bringing in rendering of molecules into CDK 1.4.x.
Which CDK version is used by the latest JChemPaint as of Feb 2012 ?