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 171274 - Jruby version not taken correctly by Netbeans
Summary: Jruby version not taken correctly by Netbeans
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: Macintosh Mac OS X
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-01 17:35 UTC by miganb
Modified: 2009-09-22 10:30 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description miganb 2009-09-01 17:35:56 UTC
This is on Netbeans 6.7.1.

Say I install a newer version of JRuby in /usr/local, update rails accordingly with this version of jruby, export the correct things in bash profile, then I install 
Netbeans.
I launch it and create a new Rails project. Then I decide this project will run on built-in JRuby.

This does not work correctly because the built.properties file in ~/.netbeans/6.7/built.properties is not updated, hence glassfish which reads it, though it 
should have read either project configuration or bash profile complains about not finding  the correct version of rails gem.

I have to remove the symbolic link in /usr/local to the new jruby version, remove the export in bash profile, remove the built.properties file to get things 
work correctly. 

Issue already discussed in netbeans forum in March 2009, and in June 2009. Take me all this time to understand where was the culprit.

Fully reproducible.
Comment 1 Tomas Danek 2009-09-02 08:16:40 UTC
adjusting priority - not a P1, P1 is reserved for crashes and data loss.

I am using on my mac successfully three platforms: built-in jruby, which comes with netbeans and is default platform for
every netbeans project, jruby installed by darwin ports, and native ruby that comes with leopard.

You should be able to use all platforms that you have registred in IDE via Ruby Platform Manager as well as manage their
gems. Just ensure in IDE in Tools|Ruby Platforms that every registred platform has correct path to interpreter, gem
home, gem tool,... 
Comment 2 miganb 2009-09-02 08:33:05 UTC
That's the theory, and I wish it would become reality, but as explained, although apparently ruby platforms are correctly detected and have correct paths to all 
tools, it does not impede that there is a mismatch between what is required in a project and what glassfish really uses, at least for me.
Jruby compiled from source by me.
I use 4 versions: latest jruby, built-in jruby, native ruby leopard, and latest ruby.
Comment 3 Erno Mononen 2009-09-07 12:55:36 UTC
Thanks for filing this, I'll investigate it. Not sure yet whether this is a problem in ruby.platform or in the 
glassfish plugin.
Comment 4 Erno Mononen 2009-09-09 12:28:56 UTC
This seems like a problem in the GF plugin, so reassigning (for me this works fine though). What platform do you have 
set for GlassFish in Tools -> Servers -> GlassFish -> JRuby? The entries in build.properties may not be causing the 
problem, the IDE just keeps there the properties of the platforms it is aware of (except for the built-in platform), 
even once they've been removed. I don't think the GF server plugin reads that file directly.

Also, please turn on detailed logging, reproduce the issue and attach the log file then (http://wiki.netbeans.org/
FaqRubyNBLogging67) - thanks in advance!
Comment 5 Vince Kraemer 2009-09-09 17:58:28 UTC
open dada request to filer
Comment 6 Michal Mocnak 2009-09-22 10:30:28 UTC
Without requested information for long time - INVALID. We can't do anything in this case. Reporter, please add requested information and reopen issue. 
Thanks in advance.