[ANN] Rawr 1.6.5 released

[James Britt]

I pushed code to the Github repo and upload a new gem to gems.neurogami.com.

What's new:

* A build_configuration.rb option, `verbose`, that will tell rawr to
spew out more details on what it is doing. Handy for when things
don't turn out as you expect.

* Compilation of ruby files appears to be working. This was a weird
one, and I'm not sure if the change I made worked because it's the right
thing or because it handles a bug in JRuby or Java, but I found that,
when you have compiled Ruby files bundled into the resulting jar,
"require" was not finding things on any $LOAD_PATH value that ended in a
slash. Main.java was set to add this trailing slash to all paths added
from the project configuration. OK, fine, but if you did not compile
the Ruby files then that trailing slash seemed to be needed. I need to
look at this more when I'm not tired but I'm releasing it because Ruby
source compilation has been declared broken for a while now, and this
only changes the behavior of Main.java of you change the config, so
worst case it's *still* broken. But perhaps if more people can try this
out we can see how robust it is while I set up some proper test code.

I don't recall *ever* having to add a trailing slash to any path i added
to $:, so I'm sort of surprised this was even there, and also surprised
that when I first removed it it broke non-compiled-ruby test code.



James Britt

[Bruce Tesar]

James, thanks for this release! It took me a little while to figure out that with this version, setting compilation of ruby source to true avoids the problem with jar creation that I was having earlier. The "slash at the end of the path" business sounds weird; I'll keep an eye out for anything that might shed light on that. But in the meantime, rawr 1.6.5 seems to be working for me!

Regards,
Bruce

[James Britt]

On Tuesday, April 2, 2013 6:16:16 PM UTC-7, Bruce Tesar wrote:

James, thanks for this release! It took me a little while to figure out that with this version, setting compilation of ruby source to true avoids the problem with jar creation that I was having earlier. The "slash at the end of the path" business sounds weird; I'll keep an eye out for anything that might shed light on that. But in the meantime, rawr 1.6.5 seems to be working for me!

Very good.  BTW, the default for the jvm is now 1.7, but that turns out to cause trouble in som cases.  it's easy enough to edit build_configuraiton.rb to use 1.6 but I think the next release of rawr will go back to defaulting to 1.6

I've been running through assorted test scenarios to see that things work OK, and so far all is cool, so I might push  out 1.6.6 before long (along with updates for Monkeybars and Swingset-ng)