installing buildr 1.3.1

[gcr]

After reading an article about switching from Maven to Buildr, I thought to
myself omg, please can it be true?  Can I leave the wretched difficult world
of maven behind me.  So off I went to get buildr installed on my Linux
(x86-32).

I tried to install the latest buildr for jruby and the ruby and am getting
the same error on both of them.

This was basically the following:

JRuby:

jruby -S gem install jruby-openssl -v 0.2
jruby -S gem install net-ssh -v 2.0.1
jruby -S gem install net-sftp -v 2.0.0
jruby -S gem install rubyforge -v 0.4.5
jruby -S gem install hoe -v 1.3.0
jruby -S gem install rspec -v 1.1.3
jruby -S gem install buildr

# which buildr
/usr/local/jruby/bin/buildr

# buildr -version
/usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:45:in
`initialize': stack level too deep (SystemStackError)
        from
/usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:45:in
`new'
        from
/usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:45:in
`create'
        from
/usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:59:in
`initialize'
        from
/usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems.rb:130:in `new'
        from
/usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems.rb:130:in `activate'
        from /usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems.rb:49:in
`gem'
        from /usr/local/jruby/bin/buildr:18
        from /usr/local/jruby/bin/buildr:19:in `load'
         ... 2086 levels...
        from /usr/local/jruby/bin/buildr:19
        from /usr/local/jruby/bin/buildr:19:in `load'
        from /usr/local/jruby/bin/buildr:19


For ruby I did a:

ruby -S gem install buildr

answered yes to a bunch of stuff...

and tried
ruby -S buildr -version
and get an amazingly similar:
/usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:209:in `search': stack
level too deep (SystemStackError)
        from /usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:208:in
`each'
        from /usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:208:in
`search'
        from /usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:189:in
`find_name'
        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:236:in `activate'
        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:75:in
`active_gem_with_options'
        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:49:in `gem'
        from /usr/local/jruby/bin/buildr:18
        from /usr/local/jruby/bin/buildr:19:in `load'
         ... 8533 levels...
        from /usr/local/jruby/bin/buildr:19:in `load'
        from /usr/local/jruby/bin/buildr:19
        from /usr/local/jruby/bin/buildr:19:in `load'
        from /usr/local/jruby/bin/buildr:19


I have tried running it several other ways and didn't have any success.

I couldn't find a search on the mailing list, but I did search w/ google for
everything I could think of involving this stack trace.

Can anyone be of assistance?

Thanks,
Geoff

[Assaf Arkin]

On Thu, Jul 24, 2008 at 10:48 AM, Geoff Ruscoe
<gcruscoe@...> wrote:
> After reading an article about switching from Maven to Buildr, I thought to
> myself omg, please can it be true?  Can I leave the wretched difficult world
> of maven behind me.  So off I went to get buildr installed on my Linux
> (x86-32).

I'm looking into this, not sure why it happens, in fact the JRuby
stack trace points at a line that doesn't seem to be doing any
recursion.

For Ruby, can you first upgrade to a more recent version of RubyGems
(JRuby 1.1.3 already uses the latest) by running:

  sudo gem update --system

Assaf

>
> I tried to install the latest buildr for jruby and the ruby and am getting
> the same error on both of them.
>
> This was basically the following:
>
> JRuby:
>
> jruby -S gem install jruby-openssl -v 0.2
> jruby -S gem install net-ssh -v 2.0.1
> jruby -S gem install net-sftp -v 2.0.0
> jruby -S gem install rubyforge -v 0.4.5
> jruby -S gem install hoe -v 1.3.0
> jruby -S gem install rspec -v 1.1.3
> jruby -S gem install buildr
>
> # which buildr
> /usr/local/jruby/bin/buildr
>
> # buildr -version
> /usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:45:in
> `initialize': stack level too deep (SystemStackError)
>        from
> /usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:45:in
> `new'
>        from
> /usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:45:in
> `create'
>        from
> /usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:59:in
> `initialize'
>        from
> /usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems.rb:130:in `new'
>        from
> /usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems.rb:130:in `activate'
>        from /usr/local/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems.rb:49:in
> `gem'
>        from /usr/local/jruby/bin/buildr:18
>        from /usr/local/jruby/bin/buildr:19:in `load'
>         ... 2086 levels...
>        from /usr/local/jruby/bin/buildr:19
>        from /usr/local/jruby/bin/buildr:19:in `load'
>        from /usr/local/jruby/bin/buildr:19
>
>
> For ruby I did a:
>
> ruby -S gem install buildr
>
> answered yes to a bunch of stuff...
>
> and tried
> ruby -S buildr -version
> and get an amazingly similar:
> /usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:209:in `search': stack
> level too deep (SystemStackError)
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:208:in
> `each'
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:208:in
> `search'
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:189:in
> `find_name'
>        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:236:in `activate'
>        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:75:in
> `active_gem_with_options'
>        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:49:in `gem'
>        from /usr/local/jruby/bin/buildr:18
>        from /usr/local/jruby/bin/buildr:19:in `load'
>         ... 8533 levels...
>        from /usr/local/jruby/bin/buildr:19:in `load'
>        from /usr/local/jruby/bin/buildr:19
>        from /usr/local/jruby/bin/buildr:19:in `load'
>        from /usr/local/jruby/bin/buildr:19
>
>
> I have tried running it several other ways and didn't have any success.
>
> I couldn't find a search on the mailing list, but I did search w/ google for
> everything I could think of involving this stack trace.
>
> Can anyone be of assistance?
>
> Thanks,
> Geoff
>

[gcr]

On Thu, Jul 24, 2008 at 5:34 PM, Assaf Arkin <arkin@...> wrote:

>
> I'm looking into this, not sure why it happens, in fact the JRuby
> stack trace points at a line that doesn't seem to be doing any
> recursion.
>
> For Ruby, can you first upgrade to a more recent version of RubyGems
> (JRuby 1.1.3 already uses the latest) by running:
>
>  sudo gem update --system
>
> Assaf
>
>

First, thanks for the response.  Really looking forward to moving past
maven.  I hope to recommend buildr to all my compadres!

I did try that for the ruby:

gem update --system
Updating RubyGems
Nothing to update

I was trying the jruby version because of the statement on the getting
started that says you can't use ruby buildr for java 1.6 projects.  Is this
still accurate?

Thanks again,
Geoff

[Assaf Arkin]

On Fri, Jul 25, 2008 at 6:39 AM, Geoff Ruscoe <gcruscoe@...> wrote:

>
>
> On Thu, Jul 24, 2008 at 5:34 PM, Assaf Arkin <arkin@...> wrote:
>>
>> I'm looking into this, not sure why it happens, in fact the JRuby
>> stack trace points at a line that doesn't seem to be doing any
>> recursion.
>>
>> For Ruby, can you first upgrade to a more recent version of RubyGems
>> (JRuby 1.1.3 already uses the latest) by running:
>>
>>  sudo gem update --system
>>
>> Assaf
>>
>
> First, thanks for the response.  Really looking forward to moving past
> maven.  I hope to recommend buildr to all my compadres!
>
> I did try that for the ruby:
>
> gem update --system
> Updating RubyGems
> Nothing to update

Debian/Ubuntu?  If so make sure to read this:
http://incubator.apache.org/buildr/getting_started.html#linux

I still have no idea why JRuby is failing on you, we just did the
1.3.2 release, and of course I had to test it out myself with JRuby
1.1.3, and I'm not seeing any problems.  Can you give it another try:

jruby -S gem install buildr -v 1.3.2

> I was trying the jruby version because of the statement on the getting
> started that says you can't use ruby buildr for java 1.6 projects.  Is this
> still accurate?

For some people it segfaults during the build, and it might be
specific to OS, setup or even the build itself.  So can't guarantee
your build will finish if you're using Ruby/JDK 1.6, but it might work
OK.

Assaf

>
> Thanks again,
> Geoff
>

[gcr]

Thanks so much for the help!

So for everyone else's benefit...

We have several ruby projects that we keep in our path so that our
development environment and execution environment are in sync, because of
this we do the following in our bashrc setup:

PATH=blah:blahblbah:blah2:$PATH
RUBYLIB=$PATH

This way all of the scripts in our paths can be run or required...  Well it
turns out this is not a good thing...

This is why something in the requires or loads was recursively being called.

So if anybody runs into a problem with the recursive calls crashing with a
stack trace ... check your RUBYLIB.

If I wanted to add this to the trouble shooting page, how would I go about
doing that?  Do I need special access?

-Geoff

[Assaf Arkin]

On Mon, Jul 28, 2008 at 2:54 PM, Geoff Ruscoe <gcruscoe@...> wrote:

>
> Thanks so much for the help!
>
> So for everyone else's benefit...
>
> We have several ruby projects that we keep in our path so that our
> development environment and execution environment are in sync, because of
> this we do the following in our bashrc setup:
>
> PATH=blah:blahblbah:blah2:$PATH
> RUBYLIB=$PATH
>
> This way all of the scripts in our paths can be run or required...  Well it
> turns out this is not a good thing...
>
> This is why something in the requires or loads was recursively being called.
>
> So if anybody runs into a problem with the recursive calls crashing with a
> stack trace ... check your RUBYLIB.
>
> If I wanted to add this to the trouble shooting page, how would I go about
> doing that?  Do I need special access?

We're handling the documentation like the source code, so it's easier
to keep the two in sync.  If you look at the doc/pages directory
you'll see the file troubleshooting.textile.  Edit it, create a patch
and upload to JIRA, just like a code patch.

http://incubator.apache.org/buildr/contributing.html#documentation

Assaf


>
> -Geoff
>
>