[ANN] JRuby 1.6.0.RC1 released

The JRuby community is pleased to announce the release of JRuby
1.6.0.RC1.

JRuby 1.6.0.RC1 is the first release candidate of JRuby 1.6.0.

JRuby 1.6.0 is the largest release of JRuby to date. This release
fixes hundreds
of user issues and brings compatibility with Ruby 1.9.2 to a very high
level. We
have made Windows a primary supported platform by adding it as a
continuous
integration platform, and JRuby 1.6 will provide Windows-based Ruby
users with
the best experience yet. This release integrates experimental support
for C
extensions based on Ruby’s C API. And as with all major releases, we
have
improved stability and performance across the board in response to
real-world
user input.

We encourage Ruby and JRuby users alike to test out 1.6.0.RC1 to help us
shake
out remaining issues. It would be especially helpful if users would
test out
1.9 mode (by passing --1.9 flag) to help us round out our 1.9.2
compatibility
before the final 1.6.0 release.

Major Features:

  • Ruby 1.9.2 language and API compatibility
    ** Not implemented: Encoding::Converter, non-ASCII identifiers, ripper,
    fiddle
  • Improved Ruby call performance
  • Built-in profiler (–profile, --profile.graph)
  • RubyGems 1.4.2
  • RSpec no longer bundled
  • Ruby-debug gem unbundled, since it installs correctly now
  • C Extension support (experimental)
  • RubyGems Maven support (preview)
  • Improved compatibility and user experience on Windows
  • jruby-complete.jar now includes 1.9 standard library
  • Embedding API refinements
  • Over 2000 commits and 265 issues resolved.


blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]

I should also mention due to a dependent project forgetting to push
their maven poms, we are unable to push RC1 until they do…So maven
users will have to wait a short amount of time until we get things
straightened out.

-Tom

On Tue, Jan 11, 2011 at 9:04 AM, Thomas E Enebo [email protected]
wrote:

level. We
before the final 1.6.0 release.

  • C Extension support (experimental)


blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]

On Jan 11, 2011, at 9:04 AM, Thomas E Enebo wrote:

The JRuby community is pleased to announce the release of JRuby 1.6.0.RC1.

Does this release ship with the jruby-win32ole gem installed by default?

cr

On Tue, Jan 11, 2011 at 9:15 AM, Chuck R. [email protected]
wrote:

On Jan 11, 2011, at 9:04 AM, Thomas E Enebo wrote:

The JRuby community is pleased to announce the release of JRuby 1.6.0.RC1.

Does this release ship with the jruby-win32ole gem installed by default?

It does for the windows installer. The -bin dist will need a gem
install jruby-win32ole (we didn’t include it in dist since most
downloaders are not for windows).

-Tom


blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]

On Tue, Jan 11, 2011 at 4:04 PM, Thomas E Enebo [email protected]
wrote:

level. We
before the final 1.6.0 release.

  • C Extension support (experimental)
  • RubyGems Maven support (preview)
  • Improved compatibility and user experience on Windows
  • jruby-complete.jar now includes 1.9 standard library
  • Embedding API refinements
  • Over 2000 commits and 265 issues resolved.

Great! Thanks a lot!

My first attempt at trying 1.9 mode failed miserably:

16:56:30 jruby.org$ vi /c/Temp/test.rb
16:56:42 jruby.org$ cat /c/Temp/test.rb

puts RUBY_VERSION

16:56:49 jruby.org$ jruby /c/Temp/test.rb
1.8.7
16:56:59 jruby.org$ jruby --1.9 /c/Temp/test.rb
Error opening script file: C:/Archives/jruby.org/c/Temp/test.rb (The
system cannot find the path specified)
16:57:06 jruby.org$

16:57:06 jruby.org$ uname -a
CYGWIN_NT-5.1 padrklemme2 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin

Somehow option --1.9 prevents recognition of the file although it
works without. Any ideas?

Kind regards

robert

On Tue, Jan 11, 2011 at 5:21 PM, Thomas E Enebo [email protected]
wrote:

On Tue, Jan 11, 2011 at 9:59 AM, Robert K.
[email protected] wrote:

On Tue, Jan 11, 2011 at 4:04 PM, Thomas E Enebo [email protected] wrote:

The JRuby community is pleased to announce the release of JRuby 1.6.0.RC1.

Opened as an issue:
http://jira.codehaus.org/browse/JRUBY-5329

Thanks for checking!

Looks like we are passing --1.9 through to point in our bash script
where we think the arg is a file…which it isn’t…

You can work around this by setting the environment variable
JRUBY_OPTS="–1.9" (e.g. JRUBY_OPTS="–1.9" jruby /c/heh.rb).

We plan on fixing this for RC2.

Nice! I have attached a script to the issue I am frequently using to
execute windows programs from cygwin prompts. Maybe you can -steal-
copy some ideas from it. :slight_smile:

Kind regards

robert

On Tue, Jan 11, 2011 at 11:09 AM, Robert K.
[email protected] wrote:

copy some ideas from it. :slight_smile:
Cool! Thanks Robert…hopefully we can steal-copy…I sort of wish
there was just some infrastructure for sh/bash launchers somewhere…

-Tom

Thank you Jruby team and community…

Is it’s too risk to covert my 1.5.6 to 1.6RC1 for production next week ?

On Tue, Jan 11, 2011 at 9:59 AM, Robert K.
[email protected] wrote:

of user issues and brings compatibility with Ruby 1.9.2 to a very high
1.9 mode (by passing --1.9 flag) to help us round out our 1.9.2 compatibility

  • Ruby-debug gem unbundled, since it installs correctly now

16:57:06 jruby.org$

16:57:06 jruby.org$ uname -a
CYGWIN_NT-5.1 padrklemme2 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin

Somehow option --1.9 prevents recognition of the file although it
works without. Any ideas?

Opened as an issue:
http://jira.codehaus.org/browse/JRUBY-5329

Looks like we are passing --1.9 through to point in our bash script
where we think the arg is a file…which it isn’t…

You can work around this by setting the environment variable
JRUBY_OPTS="–1.9" (e.g. JRUBY_OPTS="–1.9" jruby /c/heh.rb).

We plan on fixing this for RC2.

-Tom

Awesome work guys! I will be testing 1.6rc1 right away and plan to
start standardizing my code around Ruby 1.9.

Where can I get more details on the embedding API refinements?

Adam

Hello,

On Wed, Jan 12, 2011 at 5:36 PM, Adam M. [email protected]
wrote:

Awesome work guys! I will be testing 1.6rc1 right away and plan to
start standardizing my code around Ruby 1.9.

Where can I get more details on the embedding API refinements?

I just updated my blog. See
http://yokolet.blogspot.com/2010/09/new-featues-of-embedding-api-for-jruby.html
for embedding API refinments.

-Yoko

I’d recommend testing your app on 1.6.1RC1 to see if there are any
issues we need to fix, but not going to production with it unless
you’re really brave :slight_smile:

On Wed, Jan 12, 2011 at 11:52 AM, Pinit A.

Maven artifacts have now been pushed for Maven users. Sorry it took
this long to clear this up.

-Tom

On Tue, Jan 11, 2011 at 9:07 AM, Thomas E Enebo [email protected]
wrote:

  • Homepage: http://www.jruby.org/
    the best experience yet. This release integrates experimental support for C
  • jruby-complete.jar now includes 1.9 standard library


blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]


blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]

Stu wrote:

Hey support #!/usr/bin/env bash vs the non portable /bin/bash. not all
OSes put bash there.

Not all OS have a bash. /bin/sh is existent per definition and portable.

Regards
Oli

Hey support #!/usr/bin/env bash vs the non portable /bin/bash. not all
OSes put bash there.

I agree! I didn’t look at the script to see if it had any bashisms.
/bin/sh would definitely be welcome and by all means the most
portable.

btw. /bin/bash definitely screws up rvm installed jruby in freebsd.

example:

% uname -a
FreeBSD hal9000.rubyprogrammer.net 8.1-RELEASE FreeBSD 8.1-RELEASE #2:
Thu Aug 12 17:55:19 CDT 2010
[email protected]:/usr/obj/usr/src/sys/HAL9000 amd64

% rvm list

rvm rubies

ruby-1.8.7-head [ x86_64 ]
=> ruby-1.9.2-head [ x86_64 ]
rbx-head [ ]
ree-head [ x86_64 ]
ree-1.8.7-2010.02 [ x86_64 ]/home/stu/.rvm/scripts/list:
/home/stu/.rvm/rubies/jruby-1.5.5/bin/ruby: /bin/bash: bad
interpreter: No such file or directory

jruby-1.5.5 [ ]

This is a bug. It should be fixed.

~Stu

On Fri, Jan 14, 2011 at 4:50 PM, Oliver Schad

I could see making the ‘env’ change, but so far we have been unable to
get a fully-functional sh-based ‘jruby’ executable. There’s enough
bashisms we depend on that it’s hard to make a conversion…and sadly
we’re not sh experts, so we don’t know the right way to make it
happen.

If there are sh experts out there, we would appreciate help coming up
with a portable sh-based ‘jruby’ script. We have a start, in jruby.sh
(may or may not be in the distributions), but it’s missing things from
the bash version: cygwinisms, proper quoting of arguments, and so on.
I attempted to fix the quoting, but it seems sh is simply crippled
here, lacking the bash arrays we use for processing arguments. Help is
needed.

https://github.com/jruby/jruby/blob/master/bin/jruby.sh

The alternative which may help many of you would be to install the
‘jruby-launcher’ gem. This is a native executable that downloads,
installs, and replaces the ‘jruby’ command with a real binary. It
should route around any issues with bash, env, or sh.

  • Charlie

Stu wrote:

I agree! I didn’t look at the script to see if it had any bashisms.

If there were bashisms it would be a bug because bash is not a portable
dependency.

Regards
Oli

Charles Oliver N. wrote:

I could see making the ‘env’ change, but so far we have been unable to
get a fully-functional sh-based ‘jruby’ executable. There’s enough
bashisms we depend on that it’s hard to make a conversion…and sadly
we’re not sh experts, so we don’t know the right way to make it
happen.

If there are sh experts out there, we would appreciate help coming up
with a portable sh-based ‘jruby’ script.

I will take a look.

Regards
Oli

On Sat, Jan 15, 2011 at 7:40 AM, Oliver Schad
[email protected] wrote:

Charles Oliver N. wrote:

If there are sh experts out there, we would appreciate help coming up
with a portable sh-based ‘jruby’ script.

I will take a look.

Great, keep us posted. Feel free to open a bug to track it at
http://bugs.jruby.org. We can’t move to just using the sh version
unless it can do everything the bash version does, and so far nobody’s
been able to make that happen.

  • Charlie

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs