Re: [Bitext2tmx-devel] Bugs in compile by ant

[Raymond <la...@gm...>]

Hi,

> 
> > I tried the ant build file on my system and it works. Perhaps there are some differences
> > in the way paths are resolved by the IBM JVM. 
> 
> Sergio did and it worked for him too. Funny that it worked for me until that version. 
> 
> Does anyone of you have any idea on what I can do to solve the path problem?
> 

Not sure. I guess I will have to try the IBM JVM at some point to see where the 
conflict arises, unless someone else finds the source of the problem.

The crux of the problem is due to the /localization directory being outside of the
/src directory. The localizations need to be on the outside so that the user can easily
change them. The usual Java way is to have the .properties files inside the /src tree.
Having them inside is very inconvenient for the average translator who does not
want to bother opening the jar file, pull out the localization files, and then put the jar
back together later.

The fix may be simple, but trying to adjust the situation so that any JVM can be
used may not work. Could be some quirks in particular JVMs.

> > I am using Eclipse and I am able to compile both by directly using Eclipse's built in 
> > compile functionality(to .class files) and using Eclipse's ant version with the build file.
> 
> Should I try that? I have Eclipse installed but haven't used it ever.

You can. I don't think it will make a difference if you use the same JVM. Eclipse
might not even start also. I tried a different non-Sun JVM with it previously and it crashed
on startup every time. Try anyway and see what happens.

> 
> > The path to the localizations is at the top of the directory tree and the build file only
> > includes this via the manifest (MANIFEST.MF). I am not sure how to include it otherwise
> > at this very moment and I am not sure what the best practice is. Will have to look into
> > this further.
> 
> Should I wait for a while?

Can't say when I can get around to this right now. I have a few other things to sort out.
Can you try a Sun JVM?

> 
> > Does the included pre-built jar file for the application work?
> 
> No. I sent you the error message. Here it is again:

Sorry, right.

> 
> Once these problems are solved, could we retake the release of a new
> version? I wonder how difficult it would be to merge Susana's interim
> results patch with Raymond's localization and UI changes...

I'd like to see new releases sooner than later. If things proceed too slowly,
because everybody else has other responsibilities, then I will have to go at it
alone to make decisions and changes in my own versions. In that case, I will still
add the code into CVS, but also make some releases on my own project.

It shouldn't be that difficult to merge the code. I would merge her changes into
my branch because she is still putting that code into the old version, rather
than on top of the cleanup and changes I made. There will be a few loose ends 
to clean up by hand after the merge due to inconsistencies between the versions.
Following basic testing, packaging, and documentation it should be near ready
for release.

Cheers.

Raymond