"rails not installed"???

[Peter Williams-4]

I updated web-main and did a clean build of my custom config (java,
javaee, ruby, groovy) which ought to include full ruby and rails support --

According to the "New Project | Rails | ..." wizard, Rails is not installed.

Other gems installed and show they are present.  Checking the gem
repository embedded in this build shows rails 2.1.0.

so (a) I thought we were using Rails 2.3.x now so why is it an old
version and (b) even though it is an old version, why aren't we using
it?  Incompatible?

Or maybe I missed a module when I updated my config definition, but this
seems unlikely.

-Peter


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

[Erno Mononen]

Hi Peter,

Peter Williams wrote:

> I updated web-main and did a clean build of my custom config (java,
> javaee, ruby, groovy) which ought to include full ruby and rails
> support --
>
> According to the "New Project | Rails | ..." wizard, Rails is not
> installed.
>
> Other gems installed and show they are present.  Checking the gem
> repository embedded in this build shows rails 2.1.0.
>
> so (a) I thought we were using Rails 2.3.x now so why is it an old
> version and (b) even though it is an old version, why aren't we using
> it?  Incompatible?

We bundle 2.3.2, and the wizard should accept any Rails version. It
checks that the Rails gems are present and that the rails executable is
found; not sure why it complains in your case. Could you turn on
detailed logging (in Options -> Ruby -> Misc) and send the log file to me?

I assume you're trying to create a Rails project using the bundled JRuby
1.2.0, right? There might be some bug in the build scripts causing old
artifacts to be left behind, or I can't now think of another explanation
for how come you still have 2.1.0 installed.

Erno

>
> Or maybe I missed a module when I updated my config definition, but
> this seems unlikely.
>
> -Peter
>
>
> ---------------------------------------------------------------------
> 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@...

[Peter Williams-4]

Erno Mononen wrote:

> Hi Peter,
>
> Peter Williams wrote:
>> I updated web-main and did a clean build of my custom config (java,
>> javaee, ruby, groovy) which ought to include full ruby and rails
>> support --
>>
>> According to the "New Project | Rails | ..." wizard, Rails is not
>> installed.
>>
>> Other gems installed and show they are present.  Checking the gem
>> repository embedded in this build shows rails 2.1.0.
>>
>> so (a) I thought we were using Rails 2.3.x now so why is it an old
>> version and (b) even though it is an old version, why aren't we using
>> it?  Incompatible?
>
> We bundle 2.3.2, and the wizard should accept any Rails version. It
> checks that the Rails gems are present and that the rails executable
> is found; not sure why it complains in your case. Could you turn on
> detailed logging (in Options -> Ruby -> Misc) and send the log file to
> me?

Enabling logging produces no messages in the log I wasn't already
getting.  I will email it to you anyway...
>
> I assume you're trying to create a Rails project using the bundled
> JRuby 1.2.0, right? There might be some bug in the build scripts
> causing old artifacts to be left behind, or I can't now think of
> another explanation for how come you still have 2.1.0 installed.
I'm thinking build issue, but short of pulling a new repository (which
I'm not convinced will fix this), I don't know why it's doing what it's
doing.  Maybe I'm checking the wrong thing?

o.jruby.distro is supposed to build the jruby + gems folder under ruby2
cluster, correct?  I can see rails 2.3.2 in o.jruby.distro, but doing a
clean build produces a jruby 1.2.0 install under ruby2 that contains
rails 2.1.0.

I'm not sure why, I guess I need to run a full verbose build and dig
through the ant logs now.

If there is a way to invoke a build of "just the jruby distro", let me
know.  I tried building both o.jruby and o.jruby.distro and just doing
that didn't generate the correct steps to produce
nbbuild/netbeans/ruby2/jruby so there must be some other target or
defines required to make that work (or another module maybe).

-Peter

>
> Erno
>
>>
>> Or maybe I missed a module when I updated my config definition, but
>> this seems unlikely.
>>
>> -Peter
>>
>>
>> ---------------------------------------------------------------------
>> 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@...
>

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

[Peter Williams-4]

GEM_HOME and GEM_PATH in the shell's build enviroment was prohibiting
"ant install-gems" on
o.jruby.distro/unpatched_source/jruby-1.2.0/build.xml from executing
correctly.

IMO this is a bug in the build system -- it should have ignored these.  
Not sure what we can do about it though, as this build.xml comes from
jruby and they probably did it this way for a reason.

Normally I don't have these assigned, but this particular shell did due
to prior ruby stuff I'd been doing there.

-Peter

Peter Williams wrote:

>
>
> Erno Mononen wrote:
>> Hi Peter,
>>
>> Peter Williams wrote:
>>> I updated web-main and did a clean build of my custom config (java,
>>> javaee, ruby, groovy) which ought to include full ruby and rails
>>> support --
>>>
>>> According to the "New Project | Rails | ..." wizard, Rails is not
>>> installed.
>>>
>>> Other gems installed and show they are present.  Checking the gem
>>> repository embedded in this build shows rails 2.1.0.
>>>
>>> so (a) I thought we were using Rails 2.3.x now so why is it an old
>>> version and (b) even though it is an old version, why aren't we
>>> using it?  Incompatible?
>>
>> We bundle 2.3.2, and the wizard should accept any Rails version. It
>> checks that the Rails gems are present and that the rails executable
>> is found; not sure why it complains in your case. Could you turn on
>> detailed logging (in Options -> Ruby -> Misc) and send the log file
>> to me?
> Enabling logging produces no messages in the log I wasn't already
> getting.  I will email it to you anyway...
>>
>> I assume you're trying to create a Rails project using the bundled
>> JRuby 1.2.0, right? There might be some bug in the build scripts
>> causing old artifacts to be left behind, or I can't now think of
>> another explanation for how come you still have 2.1.0 installed.
> I'm thinking build issue, but short of pulling a new repository (which
> I'm not convinced will fix this), I don't know why it's doing what
> it's doing.  Maybe I'm checking the wrong thing?
>
> o.jruby.distro is supposed to build the jruby + gems folder under
> ruby2 cluster, correct?  I can see rails 2.3.2 in o.jruby.distro, but
> doing a clean build produces a jruby 1.2.0 install under ruby2 that
> contains rails 2.1.0.
>
> I'm not sure why, I guess I need to run a full verbose build and dig
> through the ant logs now.
>
> If there is a way to invoke a build of "just the jruby distro", let me
> know.  I tried building both o.jruby and o.jruby.distro and just doing
> that didn't generate the correct steps to produce
> nbbuild/netbeans/ruby2/jruby so there must be some other target or
> defines required to make that work (or another module maybe).
>
> -Peter
>>
>> Erno
>>
>>>
>>> Or maybe I missed a module when I updated my config definition, but
>>> this seems unlikely.
>>>
>>> -Peter
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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@...
>>
>
> ---------------------------------------------------------------------
> 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@...