End-of-life for JRuby 1.7.x #4112

headius · 2016-08-24T22:08:20Z

We currently plan to end our support for JRuby 1.7 at the end of 2016. We believe JRuby 9k has reached a stability and compatibility level that meets (and usually exceeds) JRuby 1.7, and maintaining two major versions is a real headache.

However, we are realistic, and we know there will be outstanding issues for people migrating from 1.7 to 9k. This bug is a placeholder for users to link all their blocking 9k items, so we can have them all in one place.

The sooner we gather these bugs, the sooner we can work toward having a 9k release that's a viable target for all current JRuby 1.7 users.

A few issues we will not be addressing:

JRuby 9k releases will always support the most-current Ruby version, give or take a version. We will not support 1.8.7, 1.9.3, 2.0, 2.1, or 2.2-specific behavior in any future releases, and once we have Ruby 2.4 support we will no longer support Ruby 2.3-specific behavior.
JRuby 9k supports Java 7 and higher at present, and we will not work to support earlier versions of Java or the JDK. The one exception would be Android, if we can figure out a way to use the Java 7 features we need there. We may drop Java 7 support some time after Java 9 is released.

Other issues, we'll deal with on a case-by-case basis. Please let us know what's keeping you from migrating to JRuby 9k.

ghost · 2016-08-25T02:10:59Z

So where is the JRuby 10000 or JRuby 10.0.0.0

cprice404 · 2016-08-25T19:10:45Z

So far, the things that are keeping us from moving are: #3928 , #3922 , #3921 , and the significantly increased memory overhead. Some of those things we may be able to work around, and it's possible we'll stumble onto a few more things after we get past those. Hoping to be able to pick back up on our efforts to explore the upgrade in the next month or two.

sfrieske · 2016-08-26T12:20:57Z

9k not yet running on AIX: #3495

tbeauvais · 2016-08-27T12:43:07Z

I know it's not your problem, but..... Since Torquebox 4 hasn't been released yet, and does not have all the features of Torquebox 3.x it would be great if Torquebox 3.x shipped with JRuby 9000 https://issues.jboss.org/browse/TORQUE-1259

creddy · 2016-08-31T18:29:58Z

Thank you all for the hard work you put into this project! It is much appreciated. Currently, this one is blocking us from moving to 9.1.3.0 #4124

headius · 2016-08-31T23:12:41Z

#4124 has been fixed for 9.1.4.0.

headius · 2016-09-08T10:19:39Z

Candidate for inclusion is #1183, too.

JasonLunn · 2017-02-18T03:33:37Z

#4365 prevents 9.1.x.x from being a viable candidate for use in production under OpenJDK 7. Is JRuby's official support going to move to 8 and above?

jruby/jruby#4112

jmiettinen · 2017-04-26T11:24:33Z

Could we get #4389 to 1.7-branch? We're not quite ready to step to 9.x branch but this would make it possible to include JRuby as a dependency instead of needing to distribute it separately to each installation.

headius · 2017-05-04T18:09:13Z

@jmiettinen I don't see why not. I know @kares had a revision, so I'll dig that up and merge that too.

obfuscoder · 2017-07-28T09:07:23Z

Is there an actual end-of-life date defined for JRuby 1.7.x by now? The initially given date (end of 2016) is obsolete. We need this info in order to decide whether and when we need to migrate.

kares · 2017-07-28T09:32:36Z

@obfuscoder the last (planned) release for JRuby 1.7.x has already happened on May/2017
some jruby-openssl gem releases will still support some of the latest 1.7.x for a while but no JRuby releases are planned at this point.

obfuscoder · 2017-07-30T18:26:39Z

Thanks for theinfo. One small follow up question tho: Will there still be fixes and releases for the 1.7.x branch for newly found security issues or won't even those issues be fixed?

enebo · 2017-07-31T14:55:06Z

@obfuscoder It is our intent to not release any more but if it was devastatingly bad security issue we may end up releasing it just to not leave anyone hanging. Thankfully, we have had very few CVEs to deal with over the years so fingers crossed...openssl is the most likely target for security problems in Ruby and that is still being maintained with backwards compat in mind (for now anyways). If an openssl problem was found then any legacy production envs could update that gem.

headius · 2017-11-21T23:05:11Z

JRuby 1.7.27 appears to be sufficient as a last release for 1.7. We shall call 1.7 officially EOL now.

see jruby/jruby#4112 for context on jruby 1.7 reaching EOL.

jruby/jruby#4112 (comment)

@grajagandev

Upstream changes (from CHANGELOG.md): ## 1.10.0 / 2019-01-04 ### Features * [MRI] Cross-built Windows gems now support Ruby 2.6 [#1842, #1850] ### Backwards incompatibilities This release ends support for: * Ruby 2.2, for which [official support ended on 2018-03-31](https://www.ruby-lang.org/en/news/2018/06/20/support-of-ruby-2-2-has-ended/) [#1841] * JRuby 1.7, for which [official support ended on 2017-11-21](jruby/jruby#4112) [#1741] ### Dependencies * [MRI] libxml2 is updated from 2.9.8 to 2.9.9 * [MRI] libxslt is updated from 1.1.32 to 1.1.33 ## 1.9.1 / 2018-12-17 ### Bug fixes * Fix a bug introduced in v1.9.0 where `XML::DocumentFragment#dup` no longer returned an instance of the callee's class, instead always returning an `XML::DocumentFragment`. This notably broke any subclass of `XML::DocumentFragment` including `HTML::DocumentFragment` as well as the Loofah gem's `Loofah::HTML::DocumentFragment`. [#1846] ## 1.9.0 / 2018-12-17 ### Security Notes * [JRuby] Upgrade Xerces dependency from 2.11.0 to 2.12.0 to address upstream vulnerability CVE-2012-0881 [#1831] (Thanks @grajagandev for reporting.) ### Notable non-functional changes * Decrease installation size by removing many unneeded files (e.g., `/test`) from the packaged gems. [#1719] (Thanks, @stevecrozz!) ### Features * `XML::Attr#value=` allows HTML node attribute values to be set to either a blank string or an empty boolean attribute. [#1800] * Introduce `XML::Node#wrap` which does what `XML::NodeSet#wrap` has always done, but for a single node. [#1531] (Thanks, @ethirajsrinivasan!) * [MRI] Improve installation experience on macOS High Sierra (Darwin). [#1812, #1813] (Thanks, @gpakosz and @nurse!) * [MRI] Node#dup supports copying a node directly to a new document. See the method documentation for details. * [MRI] DocumentFragment#dup is now more memory-efficient, avoiding making unnecessary copies. [#1063] * [JRuby] NodeSet has been rewritten to improve performance! [#1795] ### Bug fixes * `NodeSet#each` now returns `self` instead of zero. [#1822] (Thanks, @olehif!) * [MRI] Address a memory leak when using XML::Builder to create nodes with namespaces. [#1810] * [MRI] Address a memory leak when unparenting a DTD. [#1784] (Thanks, @stevecheckoway!) * [MRI] Use RbConfig::CONFIG instead of ::MAKEFILE_CONFIG to fix installations that use Makefile macros. [#1820] (Thanks, @nobu!) * [JRuby] Decrease large memory usage when making nested XPath queries. [#1749] * [JRuby] Fix failing tests on JRuby 9.2.x * [JRuby] Fix default namespaces in nodes reparented into a different document [#1774] * [JRuby] Fix support for Java 9. [#1759] (Thanks, @Taywee!) ### Dependencies * [MRI] Upgrade mini_portile2 dependency from `~> 2.3.0` to `~> 2.4.0`

jruby/jruby#4112 (comment)

* Add useful links for maintenance * Add EOL note on Ruby 2.3 * Remove MRI 2.0, 2.1 and 2.2 (long EOL) This will save build time & allow me to use new features. * Remove JRuby 1.7 (EOL) jruby/jruby#4112 (comment) * Attempt to use X.Y versions to allow automatic upgrade * Add useful note to check JRuby versions * Update documentation & changelog * Stop testing for Ruby 2.2 on Windows * Test on Ruby 2.6 (Windows)

headius added ruby 2.0-2.2 ruby 1.8 in progress JRuby 1.7.x JRuby 9000 feedback needed ruby 2.3 ruby 2.4 labels Aug 24, 2016

headius added this to the JRuby 9.2.0.0 milestone Aug 24, 2016

kares mentioned this issue Aug 25, 2016

Java 9 support #4111

Closed

2 tasks

karlhe mentioned this issue Aug 31, 2016

Syntax error for 3.0.0.rc14 fnando/i18n-js#419

Closed

JuanitoFatas mentioned this issue Sep 2, 2016

Remove a hack for JRuby 1.5 rubygems/bundler#4941

Closed

the-michael-toy mentioned this issue Sep 7, 2016

1.7.19 -- invoking UndefinedMethod.call; report at http://bugs.jruby.org #4090

Closed

karlhe mentioned this issue Sep 20, 2016

Rails5 Support ageweke/fortitude#51

Closed

3 tasks

JasonLunn mentioned this issue Nov 7, 2016

Unable to install grpc gem with JRuby grpc/grpc#6705

Closed

olleolleolle mentioned this issue Nov 22, 2016

CSV.parse tries to close a file #4298

Closed

This was referenced Jan 27, 2017

JRuby 1.7.19 fails to build on Ubuntu 14 rbenv/ruby-build#734

Closed

can't install JRuby 1.7.19 rbenv/ruby-build#718

Closed

tuzz added a commit to reevoo/sitemap_check that referenced this issue Mar 13, 2017

Drop support for end-of-life JRuby 1.7.x

ebfed4e

jruby/jruby#4112

tuzz added a commit to reevoo/sitemap_check that referenced this issue Mar 13, 2017

Drop support for end-of-life JRuby 1.7.x

d68073c

jruby/jruby#4112

headius mentioned this issue May 4, 2017

Backport 4389 #4588

Merged

enebo modified the milestones: Non-Release, JRuby 9.2.0.0 May 16, 2017

camlow325 mentioned this issue May 22, 2017

Process hangs when requiring yaml under compat-version 2.0 on JRuby 1.7.27 #4613

Open

perlun mentioned this issue Oct 5, 2017

JDK9 + 1.7.x produces io/console warnings #3611

Closed

tianon mentioned this issue Nov 15, 2017

Bump jruby docker-library/official-images#3717

Merged

headius closed this as completed Nov 21, 2017

yahonda mentioned this issue Jan 16, 2018

Proposal to drop old versions of Rails, CRuby and JRuby rsim/ruby-plsql#145

Closed

jrochkind mentioned this issue Jan 24, 2018

For 3.0: update ruby versions supported traject/traject#152

Merged

flavorjones mentioned this issue Mar 22, 2018

Drop support for JRuby 1.7 sparklemotion/nokogiri#1741

Closed

flavorjones added a commit to flavorjones/concourse-gem that referenced this issue Sep 15, 2018

remove jruby 1.7 and add jruby 9.2

f2b699f

see jruby/jruby#4112 for context on jruby 1.7 reaching EOL.

havenwood added a commit to postmodern/ruby-versions that referenced this issue Dec 6, 2018

JRuby 1.7 is past end of life.

3739b2b

jruby/jruby#4112 (comment)

thbar added a commit to thbar/kiba that referenced this issue May 12, 2019

Remove JRuby 1.7 (EOL)

ccc57bf

jruby/jruby#4112 (comment)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

End-of-life for JRuby 1.7.x #4112

End-of-life for JRuby 1.7.x #4112

headius commented Aug 24, 2016

ghost commented Aug 25, 2016

cprice404 commented Aug 25, 2016

sfrieske commented Aug 26, 2016

tbeauvais commented Aug 27, 2016

creddy commented Aug 31, 2016

headius commented Aug 31, 2016

headius commented Sep 8, 2016 •

edited

JasonLunn commented Feb 18, 2017

jmiettinen commented Apr 26, 2017 •

edited

headius commented May 4, 2017

obfuscoder commented Jul 28, 2017

kares commented Jul 28, 2017

obfuscoder commented Jul 30, 2017 •

edited

enebo commented Jul 31, 2017

headius commented Nov 21, 2017

End-of-life for JRuby 1.7.x #4112

End-of-life for JRuby 1.7.x #4112

Comments

headius commented Aug 24, 2016

ghost commented Aug 25, 2016

cprice404 commented Aug 25, 2016

sfrieske commented Aug 26, 2016

tbeauvais commented Aug 27, 2016

creddy commented Aug 31, 2016

headius commented Aug 31, 2016

headius commented Sep 8, 2016 • edited

JasonLunn commented Feb 18, 2017

jmiettinen commented Apr 26, 2017 • edited

headius commented May 4, 2017

obfuscoder commented Jul 28, 2017

kares commented Jul 28, 2017

obfuscoder commented Jul 30, 2017 • edited

enebo commented Jul 31, 2017

headius commented Nov 21, 2017

headius commented Sep 8, 2016 •

edited

jmiettinen commented Apr 26, 2017 •

edited

obfuscoder commented Jul 30, 2017 •

edited