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.
I have a Ruby project I've been working on in 6.1 for a while. When I started up 6.5b for the first time, I got the attached popup error message. The problem may be that I have both Ruby 1.9 (in /usr/local/) and standard 1.8.6 (in /usr/bin) installed on this system?
Created attachment 67303 [details] Startup error message
More information: the existing project was configured to run with local system Ruby /usr/bin/ruby, 6.5b changed that to built-in JRuby. So, two problems: - shouldn't change project properties like this - project should actually work with JRuby, especially after I downloaded 500M of NetBeans! The project is at http://rubyforge.org/projects/ape/ btw
Thanks for the report. The issue with changed platform should be fixed, issue 125409. Martin, can you comment on whether it should work also when upgrading from 6.1 (which would of course make sense)? The other issue seems to be caused by the fact that neither NetBeans nor JRuby bundles Mongrel. Does the project work with JRuby if you install Mongrel for it?
It does not work in all cases. Scenario: In 6.1, platform autodetection was performed and then the user might add other platform manually. All platforms are stored in 6.1 userdir. If you then start with new userdir, which is the case when you switched to 6.5 and not using --userdir switch, the platform autodetection is performed (for 6.5 userdir). Platform for project is stored in project's properties. So if no matching platform from project's properties is found in the userdir properties, e.g. platform added by user, than the project fallbacks to the default platform. This is not ideal and might be enhanced by e.g. storing full path to the platform in project's (private) properties. This information could be then used. For now you have to switch the platform once. This is likely the only issue here which causes the other so I'm using for tracking the problem.
Martin's scenario is still valid.