Logan Barnett wrote:
On Mar 9, 2009, at 3:57 AM, Manfred Usselmann wrote:
I assumed that it was fixed, because JRUBY-2518 is on the list of fixes
for 1.2.0RC1 and Logan thought that the fix for this issue would also
solve my problem. But JRUBY-2518 is not fixed (you bumped to 1.3) and
it also
On Mar 9, 2009, at 3:57 AM, Manfred Usselmann wrote:
I assumed that it was fixed, because JRUBY-2518 is on the list of
fixes
for 1.2.0RC1 and Logan thought that the fix for this issue would also
solve my problem. But JRUBY-2518 is not fixed (you bumped to 1.3) and
it also would not solve my i
On Sun, 08 Mar 2009 22:47:44 -0500
Charles Oliver Nutter wrote:
> Manfred: Was there a bug number for this (or is it the one you just
> filed)?
The new one: JRUBY-3478
> If it's something we claimed to have fixed, perhaps it didn't
> get merged in?
I assumed that it was fixed, because JRU
Manfred: Was there a bug number for this (or is it the one you just
filed)? If it's something we claimed to have fixed, perhaps it didn't
get merged in? Otherwise, if we don't have a bug, we won't know to fix
it...which is why it's important to get bug reports in as quickly as
possible and with
Hi,
I have just tested JRuby 1.2.0RC2 and still having a problem with the
Dir class when the directory is packaged into a jar file (in my case
with rawr).
When I run my app via the jar file sequel migrations fail while
searching for migration classes inside the given directory:
Errno::ENOENT -
The JRuby community is pleased to announce the release of JRuby 1.2.0RC2
Homepage: http://www.jruby.org/
Download: http://dist.codehaus.org/jruby/
JRuby 1.2.0RC2 has fixed many many compatibility issues and continued to
improve general performance. Due to popular demand we have a new versioning
