Am Samstag, den 13.08.2005, 21:42 +0200 schrieb Egon Willighagen: > On Saturday 13 August 2005 13:48, you wrote: > > Am Samstag, den 13.08.2005, 09:12 +0200 schrieb Egon Willighagen: > > > On Friday 12 August 2005 23:38, [EMAIL PROTECTED] wrote: > > > There's a Jmol deb package available (needs a sponsor) [1], > > > > JFTR: It needs to be updated and some circular dependencies (cdk depends > > on Jmol's JmolAPIS.jar, JmolIO.jar and Jmol depends on cdk jars) need to > > be solved. So probably Jmol needs to be split into 2 source packages or > > changed by upstream, before we seriously think about a spnsor. > > Daniel, good to see that you are on the list too :)
Of course :) > I've worked a bit on Jmol's build.xml... it's not really split up, but if you > check out Jmol CVS HEAD, and do 'ant apisio-dist'. It goes on on what you did > with the apisio.classes file, which I slightly modified... it now builds a > distrib from which I can compile jmolApis.jar and jmolIO.jar... and CDK can > be compiled using these... > > So, I hope this cleans up the circular dependency properly... Yes, this is a possible solution. One thing I want to ask: Why these classes don't go into the cdk project (into an own module, e.g. cdk-jmol.jar)? Is there any reason, that this circular dependency is still kept? Regards, Daniel ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
