Stefan,
Some testing is a good idea, and I didn't even realize there was translation
work to do.
Under the circumstances, I think it will be best for me to release my work
so far as an OpenJUMP-Ex release. This will allow other developers to give
the build a try so we can catch any lurking bugs.
Would be good to have a first test on you distribution for devel people
only.
Apart from that one issue remains... there is still to do some
translation work for several languages before an official release.
(e.g. i don't have not yet translated all german stuff)
about the bug which i worked on
tammikuuta 2007 11:15
> Vastaanottaja: List for discussion of JPP development and use.
> Aihe: Re: [JPP-Devel] Next Official Release of OpenJUMP
>
> Further to my previous email
>
> The problem with the current exe appears to be something to
> do with the classpath. Specifically I ca
[EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Puolesta Geoffrey G Roy
> Lähetetty: 24. tammikuuta 2007 11:15
> Vastaanottaja: List for discussion of JPP development and use.
> Aihe: Re: [JPP-Devel] Next Official Release of OpenJUMP
>
> Further to my previous email
>
>
Further to my previous email
The problem with the current exe appears to be something to do with the
classpath. Specifically I cannot get the OpenJUMP.exe runner to find
the JAI libraries even though they are installed. When I run OpenJUMP
from a bat file then they are found.
Geoff
Dear Su
Dear Sunburned
Just a comment on the building of an exe file for OpenJUMP. The current
exe appears to have problems in handling multiple JRE installations. On
one of my machines I have had awfull problems trying to find out which
JRE version the exe was using - to the point that I do not use
Bravo for the bugfixes!
Jon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Sunburned Surveyor
Sent: Monday, January 22, 2007 12:03 PM
To: List for discussion of JPP development and use.
Subject: [JPP-Devel] Next Official Release of OpenJUMP
I
I wanted to give everyone a brief update on the status of my work on the
next OpenJUMP release.
I have, with much help from others, "resolved" 3 bugs from the JPP
SourceForge Tracker, which was my goal for the release. We were unable to
duplicate Bug #1487099 and we determined it may have been ca