 
| View previous topic :: View next topic |
| Author |
Message |
James Moore
Posted via mailing list.
|
 Posted: Sun Oct 26, 2008 9:09 pm Post subject: Do you have multiple JRuby installations? |
 |
|
(This was posted a while ago, but I'm just getting around to reading
netbeans mail)
On Fri, Sep 26, 2008 at 8:30 AM, Chris Kutler <address-removed> wrote:
| Quote: | Hi,
Having a bundled JRuby is nice to get quickly started with the IDE, but
after using the IDE for a year, I have moved away from using the bundled
platforms.
|
Same here - the bundled version should just be ignored. It's great
for gettting your feet wet, but shouldn't be used for serious
development.
NetBeans is just an editor with a bunch of very useful features. It
seems completely obvious to me that your language wouldn't be built
into your editor. Relying on the editor to provide the language seems
completely bizarre. And I say this as a long-time Emacs user  .
| Quote: | So, I am curious. Do you just stick with the built-in JRuby and would never
consider maintaining more than one version?
|
I'd put this slightly differently - I only want to maintain one
version of JRuby, and it's not going to be the one that ships with
NetBeans.
| Quote: | Will you only upgrade your JRuby installation when you get a NetBeans
upgrade?
|
JRuby users upgrade (or not) when JRuby revs. Tying that to NetBeans
releases doesn't make sense to me.
Think about it this way - can you see someone in a dev team meeting
saying "well, we need to update JRuby for our project because I'm
using a new version of vi/TextMate/Emacs/Eclipse/NetBeans?"
| Quote: | If you have more than one JRuby platform on your system, can you talk a bit
about why. How do you set up your IDE, how do you set up your gems?
|
I only have one version of JRuby set up. The fact that NetBeans
installs another one doesn't matter much to me - it's burning a
trivial amount of space on my drive. It's a perfectly reasonable
choice to ship JRuby with NetBeans to improve the initial user
experience, but it's irrelevant to anyone who actually decides to use
NetBeans on a regular basis.
I use the gem command line tool. I don't bother to maintain the gems
in NetBeans unless it's causing a problem inside NetBeans itself. If
I have to, I might bring up the NetBeans gem manager to do this, but
it would happen so rarely that it's unimportant. (And with the new
gem support in Rails, I might change this answer to "I always use the
builtin rake tasks in Rails to tell me when I need to install gems,"
but I haven't gotten there yet.)
I do update NetBeans often (I usually just build it from a checkout of
the source tree), but I don't think that matters much. It makes an
obvious choice (ignore the builtin JRuby) mandatory - there's no way
to use the builtin stuff if you're updating NetBeans all the time.
--
James Moore
address-removed
blog.restphone.com |
|
| Back to top |
|
 |
Peter Williams
Posted via mailing list.
|
| Posted: Sun Oct 26, 2008 9:50 pm Post subject: Do you have multiple JRuby installations? |
|
|
James Moore wrote:
| Quote: | (This was posted a while ago, but I'm just getting around to reading
netbeans mail)
On Fri, Sep 26, 2008 at 8:30 AM, Chris Kutler <address-removed> wrote:
| Quote: | Hi,
Having a bundled JRuby is nice to get quickly started with the IDE, but
after using the IDE for a year, I have moved away from using the bundled
platforms.
|
Same here - the bundled version should just be ignored. It's great
for gettting your feet wet, but shouldn't be used for serious
development.
NetBeans is just an editor with a bunch of very useful features. It
seems completely obvious to me that your language wouldn't be built
into your editor. Relying on the editor to provide the language seems
completely bizarre. And I say this as a long-time Emacs user .
| Quote: | So, I am curious. Do you just stick with the built-in JRuby and would never
consider maintaining more than one version?
|
I'd put this slightly differently - I only want to maintain one
version of JRuby, and it's not going to be the one that ships with
NetBeans.
|
Thanks. This sentiment ("... I only want to maintain one version of
JRuby...") is what I would expect to be the most common. From my
perspective as the maintainer of GlassFish V3 integration, it is more
interesting to know there is one dominant version, than which particular
version it is.
If there are people actively trying to use more than one revision of
JRuby at the same time (or nearly so), that would be very helpful to
know. I'm hopeful that this number is small or non-existent at this
stage though.
| Quote: |
| Quote: | Will you only upgrade your JRuby installation when you get a NetBeans
upgrade?
|
JRuby users upgrade (or not) when JRuby revs. Tying that to NetBeans
releases doesn't make sense to me.
|
This concept works well for some languages (C/C++ and Java for example).
However, in the case of Ruby, it is more difficult. The current design
of Ruby debugging facilities is such that if you use an external Ruby or
JRuby install, you will have to maintain the debugging related gems to
be appropriate versions for what the IDE expects. In the case of JRuby,
newer revisions of JRuby have changed or deleted java integration API's
that affect systems that run JRuby in embedded mode (e.g. GlassFish
V3). Hopefully, as the platform matures, these changes will either go
away completely or be scheduled and managed.
The second issue is our problem. I don't think users should even think
about it. The first one is more interesting. Do you maintain debugging
gems? If so, is it easy? Does it bother you? Personally, I would have
preferred another solution (that didn't need maintaining by end users
for situations such as these), but that is what we have.
-Peter
| Quote: | Think about it this way - can you see someone in a dev team meeting
saying "well, we need to update JRuby for our project because I'm
using a new version of vi/TextMate/Emacs/Eclipse/NetBeans?
| Quote: | If you have more than one JRuby platform on your system, can you talk a bit
about why. How do you set up your IDE, how do you set up your gems?
|
I only have one version of JRuby set up. The fact that NetBeans
installs another one doesn't matter much to me - it's burning a
trivial amount of space on my drive. It's a perfectly reasonable
choice to ship JRuby with NetBeans to improve the initial user
experience, but it's irrelevant to anyone who actually decides to use
NetBeans on a regular basis.
I use the gem command line tool. I don't bother to maintain the gems
in NetBeans unless it's causing a problem inside NetBeans itself. If
I have to, I might bring up the NetBeans gem manager to do this, but
it would happen so rarely that it's unimportant. (And with the new
gem support in Rails, I might change this answer to "I always use the
builtin rake tasks in Rails to tell me when I need to install gems,"
but I haven't gotten there yet.)
I do update NetBeans often (I usually just build it from a checkout of
the source tree), but I don't think that matters much. It makes an
obvious choice (ignore the builtin JRuby) mandatory - there's no way
to use the builtin stuff if you're updating NetBeans all the time.
|
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
