No rake?

Ruby JRuby
1

from trunk…

C:\dev\ruby\downloads\jruby\bin>gem install faster_rubygems
JRuby limited openssl loaded. http://jruby.org/openssl
gem install jruby-openssl for full support.
Building native extensions. This could take a while…
ERROR: Error installing faster_rubygems:
ERROR: Failed to build gem native extension.

C:/dev/ruby/downloads/jruby/bin/jruby.exe mkrf_conf.rb
.
Installed–thank you for trying out – require ‘frubygems’

jrake
RUBYARCHDIR=C:/dev/ruby/downloads/jruby/lib/ruby/gems/1.8/gems/faster_rubygems-0.0.4/lib
RUBYLIBDIR=C:/dev/ruby/downloads/jruby/lib/ruby/gems/1.8/gems/faster_rubygems-0.0.4/lib
‘jrake’ is not recognized as an internal or external command,
operable program or batch file.

Is this expected?
-r

2

Hi Roger,

Yes, this is expected. By default, when you clone JRuby repo and build
it, rake is not installed.

Invoke ‘ant install-gems’ to do so. Alternatively, any task that
requires rake/rspec (like ‘ant test’, for example), will install the
rake automatically. Also, jruby -S gem install rake should work as
well.

Thanks,
–Vladimir

On Mon, Dec 21, 2009 at 3:27 PM, Roger P. [email protected]
wrote:

C:/dev/ruby/downloads/jruby/bin/jruby.exe mkrf_conf.rb
-r

Posted via http://www.ruby-forum.com/.

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
3

Vladimir S. wrote:

Hi Roger,

Yes, this is expected. By default, when you clone JRuby repo and build
it, rake is not installed.

Invoke ‘ant install-gems’ to do so. Alternatively, any task that
requires rake/rspec (like ‘ant test’, for example), will install the
rake automatically. Also, jruby -S gem install rake should work as
well.

Maybe install-gems should be run automatically when/if you do a rake
build?

-r

4

On Fri, Jan 29, 2010 at 10:40 AM, Roger P. [email protected]
wrote:

Maybe install-gems should be run automatically when/if you do a rake
build?

Yes, might be a good idea. The other option (maybe the better option)
would be that instead of installing as gems we bundle directly. I
believe 1.9 does this, with rubygems and rake included as standard
libraries. In our case, we would bundle rake, rspec, and ruby-debug as
though they were standard libraries.

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
5

On Mon, Feb 1, 2010 at 5:11 PM, Charles Oliver N.
[email protected] wrote:

On Fri, Jan 29, 2010 at 10:40 AM, Roger P. [email protected] wrote:

Maybe install-gems should be run automatically when/if you do a rake
build?

Yes, might be a good idea.

Running install-gems automatically (and without any checks) would slow
down the build significantly. We could do some tricks to detect when
to install gems and when to skip the step, but this just adds and adds
to our build file, which is pretty big already.

In this particular case, for those who clone the git repo and build
themselves, such folks probably won 't have much problem to invoke ant
install-gems or jruby -S gem install rake, or write to the alias :wink:

The other option (maybe the better option)
would be that instead of installing as gems we bundle directly.

I actually like the fact that all those “built-in” gems that we
provide, are just pre-installed gems, so that they could be easily and
safely upgraded/removed, queried, etc.

I’m not sure what “bundle directly” would mean, but if such libs would
be different from other, “external” gems, that would not be good (just
more confusion).

Thanks,
–Vladimir

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
6

On Mon, Feb 1, 2010 at 12:08 PM, Vladimir S. [email protected]
wrote:

Running install-gems automatically (and without any checks) would slow
down the build significantly. We could do some tricks to detect when
to install gems and when to skip the step, but this just adds and adds
to our build file, which is pretty big already.

I’d see this happening along the same timeframe as moving everything
to Rake, which would drastically reduce the complexity of our build
files. But I also agree, we’d need a smarter check to see if the gems
are already installed. It could be as simple as checking for them on
the filesystem under lib/ruby/gems/1.8/gems/rake, etc, which would
introduce almost no cost into the build.

In this particular case, for those who clone the git repo and build
themselves, such folks probably won 't have much problem to invoke ant
install-gems or jruby -S gem install rake, or write to the alias :wink:

Yeah, it’s easy, but it’s still an extra step you have to perform.
Ideally we should have one command people can run against a checkout
to get a fully working JRuby home, and right now it’s not obvious that
you need to install-gems.

The other option (maybe the better option)
would be that instead of installing as gems we bundle directly.

I actually like the fact that all those “built-in” gems that we
provide, are just pre-installed gems, so that they could be easily and
safely upgraded/removed, queried, etc.

I’m not sure what “bundle directly” would mean, but if such libs would
be different from other, “external” gems, that would not be good (just
more confusion).

Yeah, that’s a good point. I was mostly pointing at the bundling of
RubyGems and Rake directly into Ruby 1.9…but that already has
introduced upgrading issues for them. So maybe it’s not a good idea.

If we could just get RubyGems and Maven and embedded deployment and
classloaders and classpath and jruby-complete to all work perfectly
together, it would be a non-issue :slight_smile:

  • Charlie

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
7

In our case, we would bundle rake, rspec, and ruby-debug as
though they were standard libraries.

Sounds good to me.
-r