I committed an update to my fix for JRUBY-5114. Originally I had hoped
we could get away with never autoclosing streams, since users SHOULD
be closing them manually and not leaving them for GC to clean up.
However, that behavior is expected by so many Ruby users, I backed off
on that change.
Inste
"5E".to_f behaves differently than MRI
--
Key: JRUBY-5208
URL: http://jira.codehaus.org/browse/JRUBY-5208
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRu
ConcurrentModificationException on "rake test" in Rails 3.0.3
-
Key: JRUBY-5209
URL: http://jira.codehaus.org/browse/JRUBY-5209
Project: JRuby
Issue Type: Bug
Affects Versions:
On Wed, Nov 24, 2010 at 2:10 AM, Charles Oliver Nutter
wrote:
> I committed an update to my fix for JRUBY-5114. Originally I had hoped
> we could get away with never autoclosing streams, since users SHOULD
> be closing them manually and not leaving them for GC to clean up.
> However, that behavior
win32ole can cause odd backtrace
Key: JRUBY-5210
URL: http://jira.codehaus.org/browse/JRUBY-5210
Project: JRuby
Issue Type: Bug
Environment: jruby 1.5.5 (ruby 1.8.7 patchlevel 249) (2010-11-10
4bd42
Object.send(:eval, "self") returns caller instead of Object
---
Key: JRUBY-5211
URL: http://jira.codehaus.org/browse/JRUBY-5211
Project: JRuby
Issue Type: Bug
Components: Core
Well, I started fiddling with this migration.
Initially going with gollum format (github wiki)
https://github.com/qmx/jruby-wiki-migration
a preview of imported stuff here =>
https://github.com/qmx/jruby-wiki-migration/wiki/_pages
What do you all think?
Disclaimer: the migration code is a mess
