>> Unfortunately, I can get nowhere in trying to debug:
>> it is impossible to use the full 10.2
>> tarball on sourceforge, since it does not build (ant
>> says missing build-i18n.xml);
>
>Hmmm ... none of the jmol developers ever build from the tarball, so I am
>sure that this was never tested.
>
>Nico, can you look into this?
The problem is that the tarball doesn't contain all the necessary stuff for
i18n.
In build.xml, we need to add:
<include name="build-i18n.xml" />
at line 627
I can't do it right now. If anyone can do it, please do.
>> svn.sourceforge.net seems to be dead so no possibility to
>> pull the latest code.
>
>sourceforge seems to have had some problems over the past few weeks, but
>svn.sourceforge.net is working OK for me right now.
>
>> Can you please suggest a way forward?
>
>Please retry svn.sourceforge.net
It's probably like CVS: the anonymous access and the developper access are on
different servers. So one can work while the other is out of service.
Please try svn.sourceforge.net with a login.
>Note that Nico did some good work with using JUnit to build some test
>verification for the file readers. These tests were put in place to help
>ensure that we do not break things with the file readers.
>
>We have a molpro directory, but it only has one file in it ... vib.xml
>
>** 2 minutes later **
>
>Hmmm ... molpro/vib.xml is not being tested.
It's probably because molpro/vib.xml didn't work when I created the tests. I
commented out everything that wasn't working.
>We should get this bug resolved. Then we should work with you to identify
>some good test files to put in the molpro directory ... and we should
>enable the tests.
Agreed
Nico
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
