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.
#208: - have /tmp/rubysrc/src1/r1.rb /tmp/rubysrc/src2/r2.rb - create new ruby app with existing sources, add src1 and src2 as a source folders - run project (F6), set r1.rb as a main class - now create new configuration, and set r2.rb as a main. Try to run it: STARTING Error opening script file: r2.rb (No such file or directory) RUN COMPLETED Does it make sense to you to have support for more than one source root?? if you "require" something from another sourcefolder, you have to specify the path (full or relative) anyway. Does it have any advantage that i don't see??
> if you "require" something from another sourcefolder, you have to specify the > path(full or relative) anyway, You may add source root to the load-path (-I, $RUBYLIB, $:, ...)
I am having a similar problem but in a much simpler scenario. I updated yesterday to the latest Ruby modules (IDE support 0.14.0, Ruby Projects 0.12.0.1, Embedded Ruby 0.10.0, JRuby implementation 0.92.2) and now when I create any Ruby applciation and run it (F6) i get the following error: STARTING Error opening script file: and (The system cannot find the file specified) RUN COMPLETED THis is still the case if I open older projects which used to work. THe error is the same. If I run them from the command line (using JRuby but not the Netbeans one) things run (or not) as expected. I am running WinXP, Netbeans 6 (Dev 200702151900)
aharmellaw, can you attach your project to this issue? You can truncate (remove all contents) for all source files. I'm really just wanting to look at your nbproject directory contents, as well as know the names and locations of the source files in your project.
I believe the problem with "and" had to do with a windows Spaces in paths bug that we had quite a while back (where "and" was part of "Programs and Files" in the path.) I tried the original scenario and that seems to work fine now.
Reassigning this issue to newly created 'ruby' component.
Changing target milestone of all resolved Ruby issues from TBD to 6.0 Beta 1 build.