Ruby Gems manager wierdness

[Chris Kutler]

After I install a gem using the gems manager, its entry shows up in both
the Installed tab and New Gems tab, even after I Reload Gems.

Is this a change?

I am experiencing some oddness where things don't work when I install a
gem from the gems manager but start working when I install from the
command line (same install command as used by the gems manager).  For
example, it doesn't find the activerecord-jdbcpostgresql-adapter when
the gems manager shows it installed. Then I install on the command line
and it finds it. I had oddities with warbler too, where the command-line
warble command didn't work until I installed warbler from the command
line. Hard to pin down. Anyone else experiencing this?



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Martin Krauskopf]

Chris Kutler wrote:
> After I install a gem using the gems manager, its entry shows up in both
> the Installed tab and New Gems tab, even after I Reload Gems.

Yes, that's right. This give you a chance to:

- install newer and/or older version of a gem
- reinstall a gem when it is corrupted

Which was not possible in the past.

> Is this a change?

Yes, in 6.5.

> I am experiencing some oddness where things don't work when I install a
> gem from the gems manager but start working when I install from the
> command line (same install command as used by the gems manager).  For
> example, it doesn't find the activerecord-jdbcpostgresql-adapter when
> the gems manager shows it installed. Then I install on the command line
> and it finds it. I had oddities with warbler too, where the command-line
> warble command didn't work until I installed warbler from the command
> line. Hard to pin down. Anyone else experiencing this?

Sounds like a bug. If you can file it with the log as usually:

   http://wiki.netbeans.org/FaqRubyNBLogging

Not sure whether problem in Gem Manager or Rails part. Likely lets start
with ruby/gems component. I'll evaluate and possibly pass to Erno.

Thanks,
        m.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Chris Kutler]

This will be hard to come up with the steps to duplicate. Might take
awhile to figure out how to recreate. If anyone else experiences this,
let me know so we can compare notes.

Martin Krauskopf wrote:

> Chris Kutler wrote:
>> After I install a gem using the gems manager, its entry shows up in
>> both the Installed tab and New Gems tab, even after I Reload Gems.
>
> Yes, that's right. This give you a chance to:
>
> - install newer and/or older version of a gem
> - reinstall a gem when it is corrupted
>
> Which was not possible in the past.
>
>> Is this a change?
>
> Yes, in 6.5.
>
>> I am experiencing some oddness where things don't work when I install
>> a gem from the gems manager but start working when I install from the
>> command line (same install command as used by the gems manager).  For
>> example, it doesn't find the activerecord-jdbcpostgresql-adapter when
>> the gems manager shows it installed. Then I install on the command
>> line and it finds it. I had oddities with warbler too, where the
>> command-line warble command didn't work until I installed warbler
>> from the command line. Hard to pin down. Anyone else experiencing this?
>
> Sounds like a bug. If you can file it with the log as usually:
>
>   http://wiki.netbeans.org/FaqRubyNBLogging
>
> Not sure whether problem in Gem Manager or Rails part. Likely lets
> start with ruby/gems component. I'll evaluate and possibly pass to Erno.
>
> Thanks,
>     m.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...