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 182405 - [69cat] Unable to debug a test file using JRuby
Summary: [69cat] Unable to debug a test file using JRuby
Status: RESOLVED FIXED
Alias: None
Product: ruby
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-19 21:43 UTC by esmithbss
Modified: 2010-04-13 13:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Log File where both launch attempts were made. (487.34 KB, application/octet-stream)
2010-03-19 21:44 UTC, esmithbss 		Details
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 esmithbss 2010-03-19 21:43:34 UTC 
Product Version = NetBeans IDE Dev (Build 201003190200)
Operating System = Linux version 2.6.32-trunk-686 running on i386
Java; VM; Vendor = 1.6.0_18
Runtime = Java HotSpot(TM) Client VM 16.0-b13

When debugging under native ruby, the Debug menu's "Debug Test File" item launches a debug session for the test file in the editor or the test associated with the file in the editor.

When using the built-in JRuby, this menu item does nothing.

Either the menu item needs to be disabled when it is unavailable, or the JRuby system should launch a test process similar to the way native ruby is working.
Comment 1 esmithbss 2010-03-19 21:44:22 UTC 
Created attachment 95471 [details]
Log File where both launch attempts were made.
Comment 2 Erno Mononen 2010-03-29 11:25:41 UTC 
The action is supposed to work with JRuby too. I was able to reproduce this with a build from last week, but not with a build from today's sources. What makes it strange is that I can't think of any commit that could have caused/fixed this.
Comment 3 esmithbss 2010-03-29 14:47:13 UTC 
Perhaps it's the same fix that is prohibiting me from seeing breakpoints in plugins right now.
Comment 4 Erno Mononen 2010-04-13 13:44:46 UTC 
So I suppose the cause and the fix were not in the ruby modules. Seems to work for me with today's build too, so closing as fixed. Please reopen if needed.