jruby-rack 1.2.7 → 1.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 24de58d357962944b8e2dd77cf34c3af33e5e5f93a68ebf4f75c86666795a9a1
-  data.tar.gz: 3e19c76e147b46be50552f6df538588e023ea1fb2556c964633c16320493e84b
+  metadata.gz: 480bad7f58a728015d2d14bbf86ec8296dc3620cdd6d10a4e5d0ee7cf747d0e6
+  data.tar.gz: fc3591afbf787931dd71a41422f156b508dcd161c487672009aada3ae183caf5
 SHA512:
-  metadata.gz: 78c1c3a405e8858a390963ab7311a81ce31e3265936949b4900cd5d91b35f6b11f79b214ed46a7ce0951f9ae4f0492bfeef2379e1dedd48077038e943c70c2ba
-  data.tar.gz: e0462a4181218c7cbec0ffbb9d4dae3d0bf0fc0de80b8e971fa991056c281976afaa33a6ec873583d582b585a7dcfce8a7c79f2095d2cb445cf5598c13dbac8a
+  metadata.gz: f4d4ba89f604deebbd80d7213c69e964f18d33373c25bf80a431338d659844e62e02311300c6c3c6262cdf38c335bf290797e8f8432aeffbfbb478a1aa274c9e
+  data.tar.gz: aa83558ba91a6a38e13801a78b3d0f7540727a8673036a85aca355908010afcb10a2a168ae21449b7cc8be885e5a40862ee5bcfd2c16199fd48eafca174e9887

data/CHANGELOG.md

@@ -1,4 +1,51 @@
-## 1.2.7 (UNRELEASED)
+## 1.3.0 (UNRELEASED) 
+
+- Officially support Javax Servlet API 4.0 (JEE 8)
+- Refactor logging for more sane defaults
+- Remove long-deprecated configuration and API functionality
+
+For most users this should be a minor upgrade; as long as you do not depend on functionality deprecated within
+JRuby-Rack 1.2.x, EOL JRuby or EOL Rails versions.
+
+Breaking compatibility changes
+- Drop support for JRuby 9.x (and thus Java < 21)
+- Drop support for Rails < 7.2
+- Drop JMS support
+
+Breaking behavioral changes
+- Change context listener to throw by default in case of an exception during initialization
+- Change rails context listener to assume a thread-safe application by default
+- Rack is no longer vendored inside the jar, so applications must ensure rack is provided via bundler or GEM_PATH
+
+Breaking configuration capability changes
+- Drop `jruby.rack.jruby.version` and `jruby.rack.rack.release` keys from rack `env` Hash
+- Drop deprecated and undocumented jruby-rack 1.0 backwards compat properties `jruby.runtime.timeout.sec`, `jruby.runtime.initializer.threads`, `jruby.init.serial`, `jruby.rack.request.size.threshold.bytes`
+- Drop deprecated `jruby.rack.ignore.env` property, replaced long ago by `jruby.runtime.env` and optional `jruby.runtime.env.rubyopt`
+- Drop deprecated `jruby.rack.filter.*` properties, replaced long ago by init parameters `addsHtmlToPathInfo` and `verifiesHtmlResource`
+- Drop handling of `# rack.version` magic comments inside `config.ru` files, replaced by bundler or user-managed `GEM_PATH`
+
+Breaking Java API changes (only relevant for users extending the Java API)
+- Drop unnecessary `jruby.compat.version` and `RackConfig.getCompatVersion()` API
+- Drop deprecated `org.jruby.rack.RackInput` alias for `org.jruby.rack.ext.Input` class
+- Drop/rename deprecated `RackConfig` and `ServletRackEnvironment` API methods per their earlier comments
+- Drop deprecated `RackLogger` string (`level`) constants
+- Custom `RackLogger` implementations must accept `CharSequence` rather than `String` to allow `RubyString` passthrough 
+- Rename deprecated `JRuby::Rack::ServletLog` to `JRuby::Rack::ErrorLog` for clarity, despite usage only in servlet contexts.
+
+Breaking Ruby API changes (only relevant for users extending the Ruby API)
+- Drop deprecated `JRuby::Rack::RailsFileSystemLayout` alias for `JRuby::Rack::FileSystemLayout`
+- Drop deprecated `JRuby::Rack::Errors` alias for `JRuby::Rack::ErrorApp`
+- Drop deprecated `Rack::Handler::Servlet::Env` and `Rack::Handler::Servlet::LazyEnv` types (replaced by `DefaultEnv`)
+- Drop deprecated setting of global `$servlet_context` variable during embedded usage (replaced by `JRuby::Rack.context`)
+
+## 1.2.8
+
+- Improve isolation and bundler version/CLI boot issues with more opinionated boot process (#461)
+- Fix possible infinite loop in Response#isClientAbortException (#449, #450)
+- Fix startup logging of captured errors when config properties cannot be dumped
+- Update (bundled) rack to 2.2.24
+
+## 1.2.7
 
 - Ensure compatibility with JRuby 10.0 and 10.1 (#419, #423)
 - Ensure compatibility with Rails 8.0 (#419)
@@ -180,9 +227,9 @@ Changes from 1.1.15 apply since the previous release got yanked due a regression
   to handle custom lazy-bound keys but can not use a default proc (#132)
 - support the renew (and skip) session option with servlet store (#131)
 - improve ENV isolation with booted Ruby runtimes
-  * jruby.rack.env replaces jruby.rack.ignore.env (now deprecated)
+  * jruby.runtime.env replaces jruby.rack.ignore.env (now deprecated)
   * make sure RUBYOPT is ignored (with backwards compat)
-  * jruby.rack.env.rubyopt for finer RUBYOPT behavior control
+  * jruby.runtime.env.rubyopt for finer RUBYOPT behavior control
   * allow env value to be specified from config
 - solve the rackup "chicken - egg" problem with a plain Rack app
   * with a magic comment in config.ru # rack.version: ~>1.3.6

data/README.md

@@ -13,11 +13,12 @@ For more information on Rack, visit http://rack.github.io/.
 
 ## Compatibility
 
-| JRuby-Rack Series                                              | Status        | Rack      | JRuby      | Java | Rails     | Target Servlet API | Notes                                                          |
-|----------------------------------------------------------------|---------------|-----------|------------|------|-----------|--------------------|----------------------------------------------------------------|
-| [**1.2**](https://github.com/jruby/jruby-rack/tree/1.2-stable) | Maintained    | 2.2       | 9.3 → 10.1 | 8+   | 5.0 → 8.0 | 3.0 (Java EE 6)    | ✅ _Unofficial_: Servlet 3.1 → 4.0 also OK with most containers |
-| [**1.1**](https://github.com/jruby/jruby-rack/tree/1.1-stable) | EOL @ 2024-05 | 1.x → 2.2 | 1.6 → 9.4  | 6+   | 2.1 → 5.2 | 2.5 (Java EE 5)    | ✅ _Unofficial_: Servlet 3.0 → 4.0 also OK with most containers |
-| [**1.0**](https://github.com/jruby/jruby-rack/tree/1.0.10)     | EOL @ 2011-11 | 0.9 → 1.x | 1.1 → 1.9  | 5+   | 2.1 → 3.x | 2.5 (Java EE 5)    |                                                                |
+| JRuby-Rack Series                                              | Status        | Rack      | JRuby       | Java | Rails     | Servlet API (min → mostly supported) | Notes                                                     |
+|----------------------------------------------------------------|---------------|-----------|-------------|------|-----------|--------------------------------------|-----------------------------------------------------------|
+| [**1.3**](https://github.com/jruby/jruby-rack/tree/1.3-stable) | Maintained    | 2.2       | 10.0 → 10.1 | 21+  | 7.2 → 8.0 | 4.0 (Java EE 8)                      | ✅ _Unofficial_: Rails 6.1 → 7.1 untested, but likely OK. |
+| [**1.2**](https://github.com/jruby/jruby-rack/tree/1.2-stable) | EOL @ 2026-09 | 2.2       | 9.3 → 10.1  | 8+   | 5.0 → 8.0 | 3.0 → 4.0 (Java EE 6 → 7)            |                                                           |
+| [**1.1**](https://github.com/jruby/jruby-rack/tree/1.1-stable) | EOL @ 2024-05 | 1.x → 2.2 | 1.6 → 9.4   | 6+   | 2.1 → 5.2 | 2.5 → 4.0 (Java EE 5 → 7)            |                                                           |
+| [**1.0**](https://github.com/jruby/jruby-rack/tree/1.0.10)     | EOL @ 2011-11 | 0.9 → 1.x | 1.1 → 1.9   | 5+   | 2.1 → 3.x | 2.5 (Java EE 5)                      |                                                           |
 
 ## Getting Started
 
@@ -150,7 +151,8 @@ using is `org.jruby.rack.RackFilter`, the filter supports the following
   original URI.  However, this behavior may confuse other servlets in your 
   application that have a wildcard mapping. Defaults to true.
 - **verifiesHtmlResource** used with the previous parameter to make sure the
-  requested static resource exists before adding the .html request URI suffix
+  requested static resource exists before adding the .html request URI suffix.
+  Defaults to false.
 
 The application can also be configured to dispatch through a servlet instead of
 a filter, the servlet class name is `org.jruby.rack.RackServlet`.
@@ -179,10 +181,11 @@ Several aspects of Rails are automatically set up for you.
 ## JRuby Runtime Management
 
 JRuby runtime management and pooling is done automatically by the framework.
-In the case of Rails, runtimes are pooled by default. For other Rack applications a
-single shared runtime is created and shared for every request by default.
+For Rack-only applications (and Rails ones from jruby-rack >= 1.3), a single 
+shared runtime is created and shared for every request by default.
+
 If `jruby.min.runtimes` and `jruby.max.runtimes` values are
-specified pooling is supported for plain Rack applications as well.
+specified pooling of runtimes can be enabled for both types of applications.
 
 We do recommend to boot your runtimes up-front to avoid the cost of initializing
 one while a request kicks in and find the pool empty, this can be easily avoided
@@ -227,10 +230,9 @@ as context init parameters in web.xml or as VM-wide system properties.
 - `jruby.runtime.env`: Allows to set a custom ENV hash for your Ruby environment
   and thus insulate the application from the environment it is running. By setting
   this option to en empty string (or 'false') it acts as if the ENV hash was
-  cleared out (similar to the now deprecated `jruby.rack.ignore.env` option).
-- `jruby.runtime.env.rubyopt`: This option is used for compatibility with the
-  (deprecated) `jruby.rack.ignore.env` option since it cleared out the ENV after
-  RUBYOPT has been processed, by setting it to true ENV['RUBYOPT'] will be kept.
+  cleared out (similar to the now removed `jruby.rack.ignore.env` option).
+- `jruby.runtime.env.rubyopt`: Set to true to cause ENV['RUBYOPT']
+  to be retained even when using `jruby.runtime.env` to override the environment.
 - `jruby.rack.env.gem_path`: If set to `true` (the default) jruby-rack will
   ensure ENV['GEM_PATH'] is altered to include the `gem.path` above. If you set it to a
   value, this value will be used as GEM_PATH, overriding the environment and
@@ -255,20 +257,6 @@ as context init parameters in web.xml or as VM-wide system properties.
   been previously read this leads to a limitation (Rack won't see the POST paras).
   Thus an alternate pure 'servlet' env "conversion" is provided that maps servlet
   parameters (and cookies) directly to Rack params, avoiding Rack's input parsing.
-- `jruby.rack.filter.adds.html`:
-  **deprecated** use `addsHtmlToPathInfo` filter config init parameter.
-  The default behavior for Rails and many other Ruby applications is to add an
-  *.html* extension to the resource and attempt to handle it before serving a
-  dynamic request on the original URI.
-  However, this behavior may confuse other servlets in your application that
-  have a wildcard mapping. Defaults to true.
-- `jruby.rack.filter.verify.resource.exists`:
-  **deprecated** use `verifiesHtmlResource` filter config init parameter.
-  If `jruby.rack.filter.adds.html` is true, then this setting, when true, adds
-  an additional check using `ServletContext#getResource` to verify that the
-  *.html* resource exists. Default is false.
-  (Note that apparently some servers may not implement `getResource` in the way
-  that is expected here, so in that case this setting won't matter.)
 
 ## Initialization
 
@@ -278,24 +266,10 @@ Ruby environment before booting the application. You can create a file called
 These files, if found, will be evaluated before booting the Rack environment,
 allowing you to set environment variables, load scripts, etc.
 
-For plain Rack applications, JRuby-Rack also supports a magic comment to solve
-the "rackup" chicken-egg problem (you need Rack's builder loaded before loading
-the `config.ru`, yet you may want to setup the gem version from within the rackup
- file). As we ship with the Rack gem bundled, otherwise when executing the
-provided `config.ru` the bundled (latest) version of Rack will get loaded.
-
-Use `rack.version` to specify the Rack gem version to be loaded before rackup :
-
-```ruby
-# encoding: UTF-8
-# rack.version: ~>2.2.10 (before code is loaded gem '~>2.2.10' will be called)
-```
-
-Or the equivalent of doing `bundle exec rackup ...` if you're using Bundler :
-
-```ruby
-# rack.version: bundler (requires 'bundler/setup' before loading the script)
-```
+JRuby-Rack does not vendor Rack - the application is expected to provide it, just like 
+with other Ruby web servers. For applications depending on `jruby-rack` via jar (rather than gem),
+this means having `rack` in the `Gemfile` (usually implied by the web framework); 
+or available on the application's gem path.
 
 ## Logging
 
@@ -343,7 +317,7 @@ the generated jar should be located at `target/jruby-rack-*.jar`
 Alternatively use Rake, e.g. to build the gem (skipping specs) :
 
 ```shell
-jruby -S rake clean gem SKIP_SPECS=true
+rake clean gem SKIP_SPECS=true
 ```
 
 You can **not** use JRuby-Rack with Bundler directly from the git (or http) URL
@@ -351,25 +325,47 @@ You can **not** use JRuby-Rack with Bundler directly from the git (or http) URL
 is compiled and generated on-demand during the build (it would require us to
 package and push the .jar every time a commit changes a source file).
 
-## Releasing
+## Testing
 
-Releasing must be done by users authorized to push to the `org.jruby` group ID on https://central.sonatype.org and to push the `jruby-rack` gem to https://rubygems.org.
+JRuby-Rack is always compiled against the version defined by `jruby.compat.version` in `pom.xml`. By default, tests
+will be run with this default version.
 
-* Make sure auth is configured for "central" repository ID in your `.m2/settings.xml`
-* Update the versions in `pom.xml` and `src/main/ruby/jruby/rack/version.rb` to the release version
-* Commit the version update locally
-* Run `./mvnw deploy -Prelease` to build, sign, and push all artifacts to Maven Central staging
-* Confirm the release completes publishing at `https://central.sonatype.org`
-* `rake clean gem SKIP_SPECS=true` and push the gem
-* Tag the release version in git
-* Update the versions again to the next dev version (`-SNAPSHOT` for the Maven artifact in `pom.xml` and `.SNAPSHOT` for the gem in `version.rb`)
-* Push all commits and tags to GitHub
+Run tests against a specific JRuby version:
+
+```shell
+./mvnw test -Djruby.test.version=10.1.1.0
+```
 
-## Adding testing for new Rails versions
+Or via JRuby/Rake with the local JRuby version implied by your path:
+```shell
+bundle install
+rake spec
+```
+
+Filter for specific specs:
+
+```shell
+SPEC=src/spec/ruby/rack/application_spec.rb ./mvnw test
+# or
+SPEC=src/spec/ruby/rack/application_spec.rb rake spec
+```
+
+### Run appraisals alongside different real Rails/Rack versions
+
+JRuby-Rack defaults to run specs with a Rails stub. You can run the specs against a real Rails version using the Gemfiles
+managed by the `Appraisals` gem.
+
+```shell
+export BUNDLE_GEMFILE=gemfiles/rails72_rack22.gemfile
+bundle install
+bundle exec rake spec
+```
+
+### Adding testing for new Rails versions
 
 * Add the new version to `.github/workflows/maven.yml` under the `matrix` section
 * Add a new configuration to the `Appraisals` file, then
-    ```bundle exec appraisal generate```
+  ```bundle exec appraisal generate```
 * Generate a new stub Rails application for the new version
     ```shell
     VERSION=rails72
@@ -377,12 +373,26 @@ Releasing must be done by users authorized to push to the `org.jruby` group ID o
     rm -rf $VERSION && BUNDLE_GEMFILE=~/Projects/community/jruby-rack/gemfiles/${VERSION}_rack22.gemfile bundle exec rails new $VERSION --minimal --skip-git --skip-docker --skip-active-model --skip-active-record --skip-test --skip-system-test --skip-dev-gems --skip-bundle --skip-keeps --skip-asset-pipeline --skip-ci --skip-brakeman --skip-rubocop
     ```
 * Manual changes to make to support testing
-  * In `config/production.rb` comment out the default `config.logger` value so jruby-rack applies its own `RailsLogger`.  
+  * In `config/production.rb` comment out the default `config.logger` value so jruby-rack applies its own `RailsLogger`.
+
+## Releasing
+
+Releasing must be done by users authorized to push to the `org.jruby` group ID on https://central.sonatype.org and to push the `jruby-rack` gem to https://rubygems.org.
+
+* Make sure auth is configured for "central" repository ID in your `.m2/settings.xml`
+* Update the versions in `pom.xml` and `src/main/ruby/jruby/rack/version.rb` to the release version
+* Commit the version update locally
+* Run `./mvnw deploy -Prelease` to build, sign, and push all artifacts to Maven Central staging
+* Confirm the release completes publishing at `https://central.sonatype.org`
+* `rake clean gem SKIP_SPECS=true` and push the gem
+* Tag the release version in git
+* Update the versions again to the next dev version (`-SNAPSHOT` for the Maven artifact in `pom.xml` and `.SNAPSHOT` for the gem in `version.rb`)
+* Push all commits and tags to GitHub
 
 ## Support
 
 Please use [github][3] to file bugs, patches and/or pull requests.
-More information at the [wiki][4] or ask us at **#jruby**'s IRC channel.
+More information at the [wiki][4] or ask us on our Matrix room at **#jruby:matrix.org**.
 
 [1]: https://github.com/jruby/warbler
 [2]: https://central.sonatype.com/artifact/org.jruby.rack/jruby-rack

data/lib/jruby/rack/version.rb

@@ -8,6 +8,6 @@
 
 module JRuby
   module Rack
-    VERSION = '1.2.7'
+    VERSION = '1.3.0'
   end
 end

data/lib/jruby-rack.rb

@@ -1,7 +1,7 @@
 
 module JRubyJars
   def self.jruby_rack_jar_path
-    File.expand_path("../jruby-rack-1.2.7.jar", __FILE__)
+    File.expand_path("../jruby-rack-1.3.0.jar", __FILE__)
   end
   require jruby_rack_jar_path if defined?(JRUBY_VERSION)
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: jruby-rack
 version: !ruby/object:Gem::Version
-  version: 1.2.7
+  version: 1.3.0
 platform: ruby
 authors:
 - Nick Sieger
@@ -9,8 +9,22 @@ authors:
 - JRuby contributors
 bindir: bin
 cert_chain: []
-date: 2026-05-19 00:00:00.000000000 Z
-dependencies: []
+date: 2026-08-31 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rack
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.2.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.2.0
 description: JRuby-Rack is a combined Java and Ruby library that adapts the Java Servlet
   API to Rack. For JRuby only.
 email:
@@ -22,7 +36,7 @@ files:
 - CHANGELOG.md
 - LICENSE.txt
 - README.md
-- lib/jruby-rack-1.2.7.jar
+- lib/jruby-rack-1.3.0.jar
 - lib/jruby-rack.rb
 - lib/jruby/rack/version.rb
 homepage: http://jruby.org
@@ -36,14 +50,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.6.0
+      version: 3.4.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.3
+rubygems_version: 3.7.2
 specification_version: 4
 summary: Rack adapter for JRuby and Servlet Containers
 test_files: []