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 159582 - Cannot debug application using JRuby 1.2.0RC1
Summary: Cannot debug application using JRuby 1.2.0RC1
Status: RESOLVED DUPLICATE of bug 159206
Alias: None
Product: ruby
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-04 06:07 UTC by esmithbss
Modified: 2009-03-04 07:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Error dialog (27.11 KB, image/png)
2009-03-04 06:07 UTC, esmithbss
Details
log file (69.19 KB, text/plain)
2009-03-04 06:08 UTC, esmithbss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2009-03-04 06:07:00 UTC
I have installed NB 6.5 and added JRuby 1.2.0RC1 as a ruby platform (also added ruby-debug-ide according to
wiki.netbeans.org).

I then selected an existing project which works fine with mr 1.8.6 and 1.8.7 and jr 1.1.4 and changed it to use the new
jr 1.2.0

When I attempt to launch the program for debugging, approximately 2 seconds or less after it is launched, I receive the
attached error dialog indicating the debugger couldn't connect within 15 seconds.

As you can see by the error, the system is generating a NumberFormatException attempting to use the 0RC1 portion of the
JRuby version.

From what I am able to discern based on how the JRuby platform was added, this is coming from the JRuby Platform name or
a call to the jruby runtime itself and not the file folder for JRuby.

Unfortunately, in this instance, the 0RC1 is a valid part of the installation name and should be accepted.
Comment 1 esmithbss 2009-03-04 06:07:39 UTC
Created attachment 77684 [details]
Error dialog
Comment 2 esmithbss 2009-03-04 06:08:33 UTC
Created attachment 77685 [details]
log file
Comment 3 Erno Mononen 2009-03-04 07:38:42 UTC
Seems to be a duplicate of issue 159206, this is an issue in v3 prelude. It is fixed in later v3 builds, and 1.2.0 
final should work fine with prelude too.

*** This issue has been marked as a duplicate of 159206 ***