This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 159206 - Can't run V3 with JRuby-1.2.0RC1
Summary: Can't run V3 with JRuby-1.2.0RC1
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
: 159582 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-26 13:09 UTC by Erno Mononen
Modified: 2009-03-04 07:38 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Erno Mononen 2009-02-26 13:09:36 UTC 
Product Version: NetBeans IDE Dev (Build 200902251401)
Java: 1.6.0_10-beta; Java HotSpot(TM) 64-Bit Server VM 11.0-b11
System: Linux version 2.6.27-11-generic running on amd64; UTF-8; en_US (nb)

Steps:
1. download and register JRuby 1.2.0RC1 as a Ruby platform in the IDE
2. set V3 to use it in Server -> Tools -> JRuby
3. try to run the server => startup fails with the following exception:

Java.lang.NumberFormatException: For input string: "0RC1"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
        at java.lang.Integer.parseInt(Integer.java:456)
        at java.lang.Integer.parseInt(Integer.java:497)
        at com.sun.grizzly.jruby.RailsAdapter$JRubyVersion.<init>(RailsAdapter.java:137)
        at com.sun.grizzly.jruby.RailsAdapter$JRubyVersion.<init>(RailsAdapter.java:131)
        at com.sun.grizzly.jruby.RailsAdapter.<init>(RailsAdapter.java:110)
        at com.sun.grizzly.jruby.RubyRuntime.<init>(RubyRuntime.java:48)
        ... 22 more

I have JRuby 1.2.0RC1 installed in ~/jruby-1.2.0RC1, not sure whether the NFE is caused by the path or by the JRuby 
version number that the plugin passes to the server (if it passes any such info). If the former, I guess this may be a 
GF issue.
Comment 1 Vince Kraemer 2009-02-26 21:17:11 UTC 
it looks like v3 doesn't have this problem (though it may have others).

v3 isn't shipping with 6.7, though.

v3 Prelude probably only supports JRuby 1.1.4 (which shipped before the initial v3 Prelude release) and/or JRuby 1.1.5
(which shipped prior to the v3 Prelude ML release).

I will find a way to filter out unsupported versions from the JRuby selector combo-box in the plugin.
Comment 2 Erno Mononen 2009-02-27 06:53:25 UTC 
That's a bit of problem as we want to bundle JRuby 1.2 (final) with the IDE in 6.7. We have to somehow ensure that we 
have a working v3 / JRuby combination. I'll find an appropriate mailing list to discuss this, I'll put you to Cc.
Comment 3 Vince Kraemer 2009-03-03 22:22:41 UTC 
while discussing this issue and https://glassfish.dev.java.net/issues/show_bug.cgi?id=7235 it looks like this will not
be a problem when JRuby hits 1.2.0... since the bug is a server bug that probably will not get tickled  when JRuby hits
1.2.0 and the patch that we can put into the plugin will just prevent folks from using 1.2.0RC1 (with a nice message)...
the cost/benefit analysis says, "Close this as WONTFIX" and work on things that we can do something about...
Comment 4 Erno Mononen 2009-03-04 07:38:42 UTC 
*** Issue 159582 has been marked as a duplicate of this issue. ***