#491 Bug in current beanshell library, current source tree.

[Luke S]

There is an undetermined bug or bugs in the version of beanshell currently checked into the SVN repository.

See [5f4b87cb] for details of discovery.

• Current SVN contains bsh-2.0b5.jar (371kb) in the lib folder. This library has at least one incompatibility with a script in the scripts repo, possibly others.
• Most compiled versions have bsh-2.0b4.jar (276kb)which I suspect is living in @Peter's personal HD. This library does not have the issue.

This was discovered because the current windows binary was compiled from SVN tree, rather than Peter's personal build.

SUGGESTED FIX: Upload the second library to the source tree. AOI core code is source-compatible with both versions, but compiled bytecode is not binary compatible So one can't just trade the libraries out in an already compiled AOI.

The linked thread also has a re-build of the 3.0.2 Windows binary, which should replace the current 3.0.2 windows download.

[Peter Eastman]

Oops! Thanks for pinging me (and sorry for losing track of this one).

I'm attempting to commit 2.0b4 right now, but the SVN server appears to be down. I'll try again in a little while.

[Luke S]

SVN server has been down for some time. Its the last priority to be brought back up after the major outage last week.

[Peter Eastman]

It's back up now, and I checked in the file.

[Luke S]

I'd love to get this one closed, the source checkin now works. but the updated binary is still hanging out in the forums.

[Peter Eastman]

Are you sure? I already uploaded the most recent build I could find that you linked to.

[Luke S]

Sorry, my bad. I didn't realize that one has to go down to the individual file level to see that the file has been updated. I had assumed that the "Last modified" date at https://sourceforge.net/projects/aoi/files/ reflected when the latest file had been uploaded, rather than when the next child directory structure had changed. Everything should be good, I'll close the ticket. I'll also look at integrating the installer construction into the standard build scripts so that you can be sure of what build you're using.