jruby-rack 1.1.14 → 1.1.16
Sign up to get free protection for your applications and to get access to all the features.
- data/History.md +24 -0
- data/README.md +91 -88
- data/lib/{jruby-rack-1.1.14.jar → jruby-rack-1.1.16.jar} +0 -0
- data/lib/jruby-rack.rb +1 -1
- data/lib/jruby/rack/version.rb +1 -1
- metadata +3 -3
data/History.md
CHANGED
@@ -1,3 +1,27 @@
|
|
1
|
+
## 1.1.16 (14/08/14)
|
2
|
+
|
3
|
+
- deal with `real_path` (file-system) layout regression introduced in 1.1.15
|
4
|
+
|
5
|
+
Changes from 1.1.15 apply since the previous release got yanked due a regression.
|
6
|
+
|
7
|
+
## 1.1.15 (ya/nk/ed)
|
8
|
+
|
9
|
+
- deal with potential getParameterMap "bugs" - null values e.g. on Jetty 6 (#154)
|
10
|
+
- support filter init-param to configure whether response is handled "by default"
|
11
|
+
- no header or status set (on response capture) - should report as handled
|
12
|
+
works with Tomcat as before and serves static content with Jetty (#175)
|
13
|
+
- make sure internal servlet attributes are retrieved on `env[]` (#173)
|
14
|
+
- using our "servlet-specific" path methods in booter - we're avoiding
|
15
|
+
`File.exist?` and expanding path specifically for the application layout
|
16
|
+
this helps for a better boot in non-expanded .war scenarios
|
17
|
+
- improve app layout dir resolution - e.g. FS public path should resolve relative
|
18
|
+
- a work-around for WAS (8.5) failing on `Dir.chdir` while booting (#170)
|
19
|
+
- consider response unhandled when OPTIONS with "Allow" header set (#153)
|
20
|
+
- improved handling for jruby.compat.version (should work with jruby-head)
|
21
|
+
- start using de.saumya.mojo jruby plugins for mvn (relates to #108 as well)
|
22
|
+
this allows us to work without a GEM_HOME/GEM_PATH (local ruby install)
|
23
|
+
- use ruby-style methods for the servlet api (in our servlet_env handler)
|
24
|
+
|
1
25
|
## 1.1.14 (24/02/14)
|
2
26
|
|
3
27
|
- re-invent the ErrorApp without Rack::File and with support for 503(.html)
|
data/README.md
CHANGED
@@ -1,17 +1,23 @@
|
|
1
1
|
# JRuby-Rack
|
2
2
|
|
3
|
-
JRuby-Rack is a lightweight adapter for the Java Servlet environment that allows
|
4
|
-
any Rack-based application to run unmodified in a Java Servlet container.
|
3
|
+
JRuby-Rack is a lightweight adapter for the Java Servlet environment that allows
|
4
|
+
any Rack-based application to run unmodified in a Java Servlet container.
|
5
5
|
JRuby-Rack supports Rails as well as any Rack-compatible Ruby web framework.
|
6
6
|
|
7
7
|
For more information on Rack, visit http://rack.rubyforge.org.
|
8
8
|
|
9
9
|
[![Build Status][0]](http://travis-ci.org/jruby/jruby-rack)
|
10
10
|
|
11
|
+
## Compatibility
|
12
|
+
|
13
|
+
JRuby-Rack 1.1.x aims to be compatible with JRuby 1.6 as well as 1.7 (we do
|
14
|
+
recommend 1.7), Generally, any container that supports Java Servlet >= 2.5
|
15
|
+
(JavaEE 5) specification is supported.
|
16
|
+
|
11
17
|
## Getting Started
|
12
18
|
|
13
|
-
The most-common way to use JRuby-Rack is to get [Warbler][1].
|
14
|
-
Warbler depends on the latest version of JRuby-Rack and ensures it gets placed
|
19
|
+
The most-common way to use JRuby-Rack with a Java server is to get [Warbler][1].
|
20
|
+
Warbler depends on the latest version of JRuby-Rack and ensures it gets placed
|
15
21
|
in your WAR file when it gets built.
|
16
22
|
|
17
23
|
If you're assembling your own WAR using other means, you can install the
|
@@ -20,8 +26,8 @@ If you're assembling your own WAR using other means, you can install the
|
|
20
26
|
require 'jruby-rack'
|
21
27
|
FileUtils.cp JRubyJars.jruby_rack_jar_path, '.'
|
22
28
|
|
23
|
-
Otherwise you'll need to download the latest [jar release][2], drop it into the
|
24
|
-
*WEB-INF/lib* directory and configure the `RackFilter` in your application's
|
29
|
+
Otherwise you'll need to download the latest [jar release][2], drop it into the
|
30
|
+
*WEB-INF/lib* directory and configure the `RackFilter` in your application's
|
25
31
|
*web.xml* (see following examples).
|
26
32
|
|
27
33
|
Alternatively you can use a server built upon JRuby-Rack such as [Trinidad][3]
|
@@ -29,9 +35,9 @@ with sensible defaults, without the need to configure a deployment descriptor.
|
|
29
35
|
|
30
36
|
### Rails
|
31
37
|
|
32
|
-
Here's sample *web.xml* configuration for Rails. Note the environment and
|
33
|
-
min/max runtime parameters. For **multi-threaded** (a.k.a. `
|
34
|
-
Rails with a single runtime, set min/max both to 1. Otherwise, define the size
|
38
|
+
Here's sample *web.xml* configuration for Rails. Note the environment and
|
39
|
+
min/max runtime parameters. For **multi-threaded** (a.k.a. `threadsafe!`)
|
40
|
+
Rails with a single runtime, set min/max both to 1. Otherwise, define the size
|
35
41
|
of the runtime pool as you wish.
|
36
42
|
|
37
43
|
<context-param>
|
@@ -51,15 +57,15 @@ of the runtime pool as you wish.
|
|
51
57
|
<filter-name>RackFilter</filter-name>
|
52
58
|
<filter-class>org.jruby.rack.RackFilter</filter-class>
|
53
59
|
<!-- optional filter configuration init-params : -->
|
54
|
-
<init-param>
|
60
|
+
<init-param>
|
55
61
|
<param-name>resetUnhandledResponse</param-name>
|
56
62
|
<param-value>true</param-value> <!-- true (default), false or buffer -->
|
57
63
|
</init-param>
|
58
|
-
<init-param>
|
64
|
+
<init-param>
|
59
65
|
<param-name>addsHtmlToPathInfo</param-name>
|
60
66
|
<param-value>true</param-value> <!-- true (default), false -->
|
61
67
|
</init-param>
|
62
|
-
<init-param>
|
68
|
+
<init-param>
|
63
69
|
<param-name>verifiesHtmlResource</param-name>
|
64
70
|
<param-value>false</param-value> <!-- true, false (default) -->
|
65
71
|
</init-param>
|
@@ -75,8 +81,8 @@ of the runtime pool as you wish.
|
|
75
81
|
|
76
82
|
### (Other) Rack Applications
|
77
83
|
|
78
|
-
The main difference when using a non-Rails Rack application is that JRuby-Rack
|
79
|
-
looks for a "rackup" file named **config.ru** in `WEB-INF/config.ru` or
|
84
|
+
The main difference when using a non-Rails Rack application is that JRuby-Rack
|
85
|
+
looks for a "rackup" file named **config.ru** in `WEB-INF/config.ru` or
|
80
86
|
`WEB-INF/*/config.ru`. Here's a sample *web.xml* configuration :
|
81
87
|
|
82
88
|
<filter>
|
@@ -93,7 +99,7 @@ looks for a "rackup" file named **config.ru** in `WEB-INF/config.ru` or
|
|
93
99
|
<listener-class>org.jruby.rack.RackServletContextListener</listener-class>
|
94
100
|
</listener>
|
95
101
|
|
96
|
-
If you don't have a *config.ru* or don't want to include it in your web app, you
|
102
|
+
If you don't have a *config.ru* or don't want to include it in your web app, you
|
97
103
|
can embed it directly in the *web.xml* as follows (using Sinatra as an example):
|
98
104
|
|
99
105
|
<context-param>
|
@@ -113,61 +119,61 @@ Be sure to escape angle-brackets for XML !
|
|
113
119
|
|
114
120
|
## Servlet Filter
|
115
121
|
|
116
|
-
JRuby-Rack's main mode of operation is as a filter. This allows requests for
|
117
|
-
static content to pass through and be served by the application server.
|
118
|
-
Dynamic requests only happen for URLs that don't have a corresponding file, much
|
119
|
-
like many Ruby/Rack applications expect. The (default) filter we recommend
|
120
|
-
using is `org.jruby.rack.RackFilter`, the filter supports the following
|
122
|
+
JRuby-Rack's main mode of operation is as a filter. This allows requests for
|
123
|
+
static content to pass through and be served by the application server.
|
124
|
+
Dynamic requests only happen for URLs that don't have a corresponding file, much
|
125
|
+
like many Ruby/Rack applications expect. The (default) filter we recommend
|
126
|
+
using is `org.jruby.rack.RackFilter`, the filter supports the following
|
121
127
|
(optional) init-params:
|
122
128
|
|
123
|
-
- **responseNotHandledStatuses** which statuses (when a filter chain returns)
|
124
|
-
should be considered that the response has not been handled (default value:
|
129
|
+
- **responseNotHandledStatuses** which statuses (when a filter chain returns)
|
130
|
+
should be considered that the response has not been handled (default value:
|
125
131
|
"403,404,405") and should be dispatched as a Rack application
|
126
132
|
- **resetUnhandledResponse** whether an unhandled response from the filter chain
|
127
|
-
gets reset (accepts values "true", "false" and "buffer" to reset the buffer
|
133
|
+
gets reset (accepts values "true", "false" and "buffer" to reset the buffer
|
128
134
|
only), by default "true"
|
129
|
-
- **addsHtmlToPathInfo** controls whether the .html suffix is added to the URI
|
135
|
+
- **addsHtmlToPathInfo** controls whether the .html suffix is added to the URI
|
130
136
|
when checking if the request is for a static page
|
131
137
|
- **verifiesHtmlResource** used with the previous parameter to makee sure the
|
132
138
|
requested static resource exist before adding the .html request URI suffix
|
133
139
|
|
134
|
-
The application can also be configured to dispatch through a servlet instead of
|
140
|
+
The application can also be configured to dispatch through a servlet instead of
|
135
141
|
a filter, the servlet class name is `org.jruby.rack.RackServlet`.
|
136
142
|
|
137
143
|
## Servlet Environment Integration
|
138
144
|
|
139
|
-
- servlet context is accessible to any application through the Rack environment
|
145
|
+
- servlet context is accessible to any application through the Rack environment
|
140
146
|
variable *java.servlet_context* (as well as the `$servlet_context` global).
|
141
147
|
- the (native) servlet request and response objects could be obtained via the
|
142
148
|
*java.servlet_request* and *java.servlet_response* keys
|
143
149
|
- all servlet request attributes are passed through to the Rack environment (and
|
144
150
|
thus might override request headers or Rack environment variables)
|
145
|
-
- servlet sessions can be used as a (java) session store for Rails, session
|
146
|
-
attributes with String keys (and String, numeric, boolean, or java
|
151
|
+
- servlet sessions can be used as a (java) session store for Rails, session
|
152
|
+
attributes with String keys (and String, numeric, boolean, or java
|
147
153
|
object values) are automatically copied to the servlet session for you.
|
148
154
|
|
149
155
|
## Rails
|
150
156
|
|
151
157
|
Several aspects of Rails are automatically set up for you.
|
152
158
|
|
153
|
-
- `ActionController::Base.relative_url_root` is set for you automatically
|
159
|
+
- `ActionController::Base.relative_url_root` is set for you automatically
|
154
160
|
according to the context root where your webapp is deployed.
|
155
161
|
- `Rails.logger` output is redirected to the application server log.
|
156
162
|
- Page caching and asset directories are configured appropriately.
|
157
163
|
|
158
164
|
## JRuby Runtime Management
|
159
165
|
|
160
|
-
JRuby runtime management and pooling is done automatically by the framework.
|
161
|
-
In the case of Rails, runtimes are pooled by default (the default will most
|
162
|
-
likely change with the adoption of Rails 4.0). For other Rack applications a
|
163
|
-
single shared runtime is created and shared for every request by default.
|
164
|
-
As of **1.1.9** if *jruby.min.runtimes* and *jruby.max.runtimes* values are
|
166
|
+
JRuby runtime management and pooling is done automatically by the framework.
|
167
|
+
In the case of Rails, runtimes are pooled by default (the default will most
|
168
|
+
likely change with the adoption of Rails 4.0). For other Rack applications a
|
169
|
+
single shared runtime is created and shared for every request by default.
|
170
|
+
As of **1.1.9** if *jruby.min.runtimes* and *jruby.max.runtimes* values are
|
165
171
|
specified pooling is supported for plain Rack applications as well.
|
166
172
|
|
167
173
|
We do recommend to boot your runtimes up-front to avoid the cost of initializing
|
168
174
|
one while a request kicks in and find the pool empty, this can be easily avoided
|
169
|
-
by setting *jruby.min.runtimes* equal to *jruby.max.runtimes*. You might also
|
170
|
-
want to consider
|
175
|
+
by setting *jruby.min.runtimes* equal to *jruby.max.runtimes*. You might also
|
176
|
+
want to consider tuning the *jruby.runtime.acquire.timeout* parameter to not
|
171
177
|
wait too long when all (max) runtimes from the pool are busy.
|
172
178
|
|
173
179
|
## JRuby-Rack Configuration
|
@@ -175,89 +181,89 @@ wait too long when all (max) runtimes from the pool are busy.
|
|
175
181
|
JRuby-Rack can be configured by setting these key value pairs either
|
176
182
|
as context init parameters in web.xml or as VM-wide system properties.
|
177
183
|
|
178
|
-
- `rackup`: Rackup script for configuring how the Rack application is mounted.
|
179
|
-
Required for Rack-based applications other than Rails. Can be omitted if a
|
184
|
+
- `rackup`: Rackup script for configuring how the Rack application is mounted.
|
185
|
+
Required for Rack-based applications other than Rails. Can be omitted if a
|
180
186
|
*config.ru* is included in the application root.
|
181
|
-
- `public.root`: Relative path to the location of your application's static
|
187
|
+
- `public.root`: Relative path to the location of your application's static
|
182
188
|
assets. Defaults to */*.
|
183
|
-
- `rails.root`: Root path to the location of the Rails application files.
|
189
|
+
- `rails.root`: Root path to the location of the Rails application files.
|
184
190
|
Defaults to */WEB-INF*.
|
185
191
|
- `rails.env`: Specify the Rails environment to run. Defaults to 'production'.
|
186
|
-
- `rails.relative_url_append`: Specify a path to be appended to the
|
192
|
+
- `rails.relative_url_append`: Specify a path to be appended to the
|
187
193
|
`ActionController::Base.relative_url_root` after the context path. Useful
|
188
|
-
for running a rails app from the same war as an existing app, under a
|
194
|
+
for running a rails app from the same war as an existing app, under a
|
189
195
|
sub-path of the main servlet context root.
|
190
196
|
- `gem.path`: Relative path to the bundled gem repository. Defaults to
|
191
197
|
*/WEB-INF/gems*.
|
192
|
-
- `jruby.compat.version`: Set to "1.8" or "1.9" to make JRuby run a specific
|
198
|
+
- `jruby.compat.version`: Set to "1.8" or "1.9" to make JRuby run a specific
|
193
199
|
version of Ruby (same as the --1.8 / --1.9 command line flags).
|
194
|
-
- `jruby.min.runtimes`: For non-threadsafe Rails applications using a runtime
|
200
|
+
- `jruby.min.runtimes`: For non-threadsafe Rails applications using a runtime
|
195
201
|
pool, specify an integer minimum number of runtimes to hold in the pool.
|
196
|
-
- `jruby.max.runtimes`: For non-threadsafe Rails applications, an integer
|
202
|
+
- `jruby.max.runtimes`: For non-threadsafe Rails applications, an integer
|
197
203
|
maximum number of runtimes to keep in the pool.
|
198
|
-
- `jruby.runtime.init.threads`: How many threads to use for initializing
|
204
|
+
- `jruby.runtime.init.threads`: How many threads to use for initializing
|
199
205
|
application runtimes when pooling is used (default is 4).
|
200
206
|
It does not make sense to set this value higher than `jruby.max.runtimes`.
|
201
|
-
- `jruby.runtime.init.serial`: When using runtime pooling, this flag indicates
|
202
|
-
that the pool should be created serially in the foreground rather than
|
207
|
+
- `jruby.runtime.init.serial`: When using runtime pooling, this flag indicates
|
208
|
+
that the pool should be created serially in the foreground rather than
|
203
209
|
spawning (background) threads, it's by default off (set to false).
|
204
210
|
For environments where creating threads is not permitted.
|
205
211
|
- `jruby.runtime.acquire.timeout`: The timeout in seconds (default 10) to use
|
206
|
-
when acquiring a runtime from the pool (while a pool maximum is set), an
|
212
|
+
when acquiring a runtime from the pool (while a pool maximum is set), an
|
207
213
|
exception will be thrown if a runtime can not be acquired within this time (
|
208
214
|
accepts decimal values for fine tuning e.g. 1.25).
|
209
215
|
- `jruby.runtime.env`: Allows to set a custom ENV hash for your Ruby environment
|
210
|
-
and thus insulate the application from the environment it is running. By setting
|
211
|
-
this option to en empty string (or 'false') it acts as if the ENV hash was
|
216
|
+
and thus insulate the application from the environment it is running. By setting
|
217
|
+
this option to en empty string (or 'false') it acts as if the ENV hash was
|
212
218
|
cleared out (similar to the now deprecated `jruby.rack.ignore.env` option).
|
213
|
-
- `jruby.runtime.env.rubyopt`: This option is used for compatibility with the
|
219
|
+
- `jruby.runtime.env.rubyopt`: This option is used for compatibility with the
|
214
220
|
(deprecated) `jruby.rack.ignore.env` option since it cleared out the ENV after
|
215
221
|
RUBYOPT has been processed, by setting it to true ENV['RUBYOPT'] will be kept.
|
216
222
|
- `jruby.rack.logging`: Specify the logging device to use. Defaults to
|
217
223
|
`servlet_context`. See below.
|
218
|
-
- `jruby.rack.request.size.initial.bytes`: Initial size for request body memory
|
219
|
-
buffer, see also `jruby.rack.request.size.maximum.bytes`
|
224
|
+
- `jruby.rack.request.size.initial.bytes`: Initial size for request body memory
|
225
|
+
buffer, see also `jruby.rack.request.size.maximum.bytes` below.
|
220
226
|
- `jruby.rack.request.size.maximum.bytes`: The maximum size for the request in
|
221
227
|
memory buffer, if the body is larger than this it gets spooled to a tempfile.
|
222
|
-
- `jruby.rack.response.dechunk`: Set to false to turn off response dechunking
|
228
|
+
- `jruby.rack.response.dechunk`: Set to false to turn off response dechunking
|
223
229
|
(Rails since 3.1 chunks response on `render stream: true`), it's on by default
|
224
230
|
as frameworks such as Rails might use `Rack::Chunked::Body` as a Rack response
|
225
231
|
body but since most servlet containers perform dechunking automatically things
|
226
232
|
might end double-chunked in such cases.
|
227
|
-
- `jruby.rack.handler.env`: **EXPERIMENTAL** Allows to change Rack's behavior
|
228
|
-
on obtaining the Rack environment. The default behavior is that parameter
|
229
|
-
parsing is left to be done by the Rack::Request itself (by consuming the
|
230
|
-
request body in case of a POST), but if the servlet request's input stream has
|
233
|
+
- `jruby.rack.handler.env`: **EXPERIMENTAL** Allows to change Rack's behavior
|
234
|
+
on obtaining the Rack environment. The default behavior is that parameter
|
235
|
+
parsing is left to be done by the Rack::Request itself (by consuming the
|
236
|
+
request body in case of a POST), but if the servlet request's input stream has
|
231
237
|
been previously read this leads to a limitation (Rack won't see the POST paras).
|
232
238
|
Thus an alternate pure 'servlet' env "conversion" is provided that maps servlet
|
233
239
|
parameters (and cookies) directly to Rack params, avoiding Rack's input parsing.
|
234
|
-
- `jruby.rack.filter.adds.html`:
|
240
|
+
- `jruby.rack.filter.adds.html`:
|
235
241
|
**deprecated** use `addsHtmlToPathInfo` filter config init parameter.
|
236
|
-
The default behavior for Rails and many other Ruby applications is to add an
|
237
|
-
*.html* extension to the resource and attempt to handle it before serving a
|
238
|
-
dynamic request on the original URI.
|
239
|
-
However, this behavior may confuse other servlets in your application that
|
242
|
+
The default behavior for Rails and many other Ruby applications is to add an
|
243
|
+
*.html* extension to the resource and attempt to handle it before serving a
|
244
|
+
dynamic request on the original URI.
|
245
|
+
However, this behavior may confuse other servlets in your application that
|
240
246
|
have a wildcard mapping. Defaults to true.
|
241
|
-
- `jruby.rack.filter.verify.resource.exists`:
|
247
|
+
- `jruby.rack.filter.verify.resource.exists`:
|
242
248
|
**deprecated** use `verifiesHtmlResource` filter config init parameter.
|
243
|
-
If `jruby.rack.filter.adds.html` is true, then this setting, when true, adds
|
244
|
-
an additional check using `ServletContext#getResource` to verify that the
|
245
|
-
*.html* resource exists. Default is false.
|
246
|
-
(Note that apparently some servers may not implement `getResource` in the way
|
249
|
+
If `jruby.rack.filter.adds.html` is true, then this setting, when true, adds
|
250
|
+
an additional check using `ServletContext#getResource` to verify that the
|
251
|
+
*.html* resource exists. Default is false.
|
252
|
+
(Note that apparently some servers may not implement `getResource` in the way
|
247
253
|
that is expected here, so in that case this setting won't matter.)
|
248
254
|
|
249
255
|
## Initialization
|
250
256
|
|
251
|
-
There are often cases where you need to perform custom initialization of the
|
252
|
-
Ruby environment before booting the application. You can create a file called
|
253
|
-
*META-INF/init.rb* or *WEB-INF/init.rb* inside the war file for this purpose.
|
254
|
-
These files, if found, will be evaluated before booting the Rack environment,
|
257
|
+
There are often cases where you need to perform custom initialization of the
|
258
|
+
Ruby environment before booting the application. You can create a file called
|
259
|
+
*META-INF/init.rb* or *WEB-INF/init.rb* inside the war file for this purpose.
|
260
|
+
These files, if found, will be evaluated before booting the Rack environment,
|
255
261
|
allowing you to set environment variables, load scripts, etc.
|
256
262
|
|
257
263
|
For plain Rack applications, JRuby-Rack also supports a magic comment to solve
|
258
264
|
the "rackup" chicken-egg problem (you need Rack's builder loaded before loading
|
259
265
|
the *config.ru*, yet you may want to setup the gem version from within the rackup
|
260
|
-
file). As we ship with the Rack gem bundled, otherwise when executing the
|
266
|
+
file). As we ship with the Rack gem bundled, otherwise when executing the
|
261
267
|
provided *config.ru* the bundled (latest) version of Rack will get loaded.
|
262
268
|
|
263
269
|
Use **rack.version** to specify the Rack gem version to be loaded before rackup :
|
@@ -272,18 +278,18 @@ Or the equivalent of doing `bundle exec rackup ...` if you're using Bundler :
|
|
272
278
|
|
273
279
|
## Logging
|
274
280
|
|
275
|
-
JRuby-Rack sets up a delegate logger for Rails that sends logging output to
|
276
|
-
`javax.servlet.ServletContext#log` by default. If you wish to use a different
|
281
|
+
JRuby-Rack sets up a delegate logger for Rails that sends logging output to
|
282
|
+
`javax.servlet.ServletContext#log` by default. If you wish to use a different
|
277
283
|
logging system, configure `jruby.rack.logging` as follows:
|
278
284
|
|
279
285
|
- `servlet_context` (default): Sends log messages to the servlet context.
|
280
286
|
- `stdout`: Sends log messages to the standard output stream `System.out`.
|
281
|
-
- `slf4j`: Sends log messages to SLF4J. SLF4J configuration is left up to you,
|
287
|
+
- `slf4j`: Sends log messages to SLF4J. SLF4J configuration is left up to you,
|
282
288
|
please refer to http://www.slf4j.org/docs.html .
|
283
289
|
- `log4j`: Sends log messages to log4J. Again, Log4J configuration is
|
284
290
|
left up to you, consult http://logging.apache.org/log4j/ .
|
285
|
-
- `commons_logging`: Routes logs to commons-logging. You still need to configure
|
286
|
-
an underlying logging implementation with JCL. We recommend using the logger
|
291
|
+
- `commons_logging`: Routes logs to commons-logging. You still need to configure
|
292
|
+
an underlying logging implementation with JCL. We recommend using the logger
|
287
293
|
library wrapper directly if possible, see http://commons.apache.org/logging/ .
|
288
294
|
- `jul`: Directs log messages via Java's core logging facilities (util.logging).
|
289
295
|
|
@@ -298,7 +304,7 @@ Checkout the JRuby-Rack code using [git](http://git-scm.com/) :
|
|
298
304
|
git clone git://github.com/jruby/jruby-rack.git
|
299
305
|
cd jruby-rack
|
300
306
|
|
301
|
-
Ensure you have [Maven](http://maven.apache.org/) installed.
|
307
|
+
Ensure you have [Maven](http://maven.apache.org/) installed.
|
302
308
|
It is required for downloading jar artifacts that JRuby-Rack depends on.
|
303
309
|
|
304
310
|
Build the .jar using Maven :
|
@@ -313,21 +319,18 @@ Alternatively use Rake, e.g. to build the gem (skipping specs) :
|
|
313
319
|
|
314
320
|
You can **not** use JRuby-Rack with Bundler directly from the git (or http) URL
|
315
321
|
(`gem 'jruby-rack', :github => 'jruby/jruby-rack'`) since the included .jar file
|
316
|
-
is compiled and generated on-demand during the build (it would require us to
|
322
|
+
is compiled and generated on-demand during the build (it would require us to
|
317
323
|
package and push the .jar every time a commit changes a source file).
|
318
324
|
|
319
325
|
|
320
326
|
## Support
|
321
327
|
|
322
|
-
Please use [github][4] to file bugs, patches and pull requests.
|
328
|
+
Please use [github][4] to file bugs, patches and/or pull requests.
|
323
329
|
More information at the [wiki][5] or ask us at the #jruby IRC channel.
|
324
330
|
|
325
|
-
If you need more help (e.g. migrating your application to JRuby/JRuby-Rack)
|
326
|
-
feel free to contact the current [maintainer](https://github.com/kares).
|
327
|
-
|
328
331
|
[0]: https://secure.travis-ci.org/jruby/jruby-rack.png?branch=master
|
329
332
|
[1]: http://caldersphere.rubyforge.org/warbler
|
330
333
|
[2]: http://repository.codehaus.org/org/jruby/rack/jruby-rack/
|
331
|
-
[3]:
|
332
|
-
[4]:
|
333
|
-
[5]:
|
334
|
+
[3]: https://github.com/trinidad/trinidad
|
335
|
+
[4]: https://github.com/jruby/jruby-rack/issues
|
336
|
+
[5]: https://wiki.github.com/jruby/jruby-rack
|
Binary file
|
data/lib/jruby-rack.rb
CHANGED
data/lib/jruby/rack/version.rb
CHANGED
metadata
CHANGED
@@ -2,7 +2,7 @@
|
|
2
2
|
name: jruby-rack
|
3
3
|
version: !ruby/object:Gem::Version
|
4
4
|
prerelease:
|
5
|
-
version: 1.1.
|
5
|
+
version: 1.1.16
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
8
8
|
- Nick Sieger
|
@@ -10,7 +10,7 @@ autorequire:
|
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
12
|
|
13
|
-
date: 2014-
|
13
|
+
date: 2014-08-14 00:00:00 Z
|
14
14
|
dependencies: []
|
15
15
|
|
16
16
|
description: JRuby-Rack is a combined Java and Ruby library that adapts the Java Servlet API to Rack. For JRuby only.
|
@@ -26,7 +26,7 @@ files:
|
|
26
26
|
- History.md
|
27
27
|
- LICENSE.txt
|
28
28
|
- README.md
|
29
|
-
- lib/jruby-rack-1.1.
|
29
|
+
- lib/jruby-rack-1.1.16.jar
|
30
30
|
- lib/jruby-rack.rb
|
31
31
|
- lib/jruby/rack/version.rb
|
32
32
|
homepage: http://jruby.org
|