log4jruby 2.0.0.rc3-java → 2.0.1-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e08e6f11c96bbf03b26bad478e93323c326f6c88
-  data.tar.gz: e4dd8ee67b8ed0ab344a208e23859eee67f9de69
+  metadata.gz: 8355e0417b5b8fa90580b2b5d47380ed4c70d634
+  data.tar.gz: 1a981572aafc5d7350c2aa0c2975bcec80a39976
 SHA512:
-  metadata.gz: 2bd9e0c102ab901c70a072b5e9b8d77b094a7ae1d242b723e9e7f189c9d87e77c1ac5b17e57e0ffe5554cc4ebf159c27be2723d99b6bafe9d446155d8a3b2cbf
-  data.tar.gz: aa40158379e0b483da052794623a22669213542026d439b4f88cedd35bc4a9176ccc9681bda1e76950577de3c3903c56c07d3bc2160686347de58e538913e781
+  metadata.gz: 2100d066da86f23d7a5a7d818d5e46bbb6811630d853def7c869acb0930e2c23e913039e8b5e63a56aba7fa0683c21d8f97f3310b788988a151dceb7b9af9442
+  data.tar.gz: abe6cbfceb161761850e867c5f9df6d339f7e3807ba9bb104822fca7db2b380c9fdd147c22f713e1678b6a1c919936ba5b04f9ce71980e1da7154b1f0c61be85

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # log4jruby Changelog
 
+## v2.0.1
+
+* JRuby 9K compatibility - https://github.com/lenny/log4jruby/issues/14
+
+## v2.0.0
+
+* Documentation additions, corrections.
+
 ## v2.0.0.rc3
 
 * Add Logger#silence for ActiveSupport::Logger compatibility - https://github.com/lenny/log4jruby/pull/11

data/{README.rdoc → README.md}

@@ -1,26 +1,26 @@
 
 
-= Log4jruby
+# Log4jruby
 
 * https://github.com/lenny/log4jruby
 
-== Description:
+## Description:
 
 Log4jruby is a thin wrapper around the {Log4j Logger}[http://logging.apache.org/log4j/1.2/apidocs/index.html].
 It is geared more toward those who are using JRuby to integrate with and build on top of Java code that uses Log4j.
-The <tt>Log4jruby::Logger</tt> provides an interface much like the standard ruby {Logger}[http://ruby-doc.org/core/classes/Logger.html].
+The ```Log4jruby::Logger``` provides an interface much like the standard ruby [Logger](http://ruby-doc.org/core/classes/Logger.html).
 Logging is configured via traditional Log4j methods.
 
-The primary use case(i.e. mine) for this library is that you are already up and running with Log4j and now you want
+The primary use case (i.e., mine) for this library is that you are already up and running with Log4j and now you want
 to use it for your Ruby code too. There is not much help here for configuration. In our environment, we deploy Rails
 apps that call and extend Java code into Tomcat as WARs and use a log4j.properties to configure. For the most part,
 all there is to using log4jruby is making sure the log4j jar is <tt>required</tt> and that Log4j is at least minimally
-configured(e.g. log4j.properties in the CLASSPATH). The examples should give you the idea.
+configured (e.g., log4j.properties in the CLASSPATH). The examples should give you the idea.
 
-=== Features
+### Features
 
-* Filename, line number, and method name are available(if tracing is on) to your appender layout via {MDC}[http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/MDC.html].
-* Exceptions can be logged directly and are output with backtraces. Java Exceptions(i.e. NativeExceptions)
+* Filename, line number, and method name are available (if tracing is on) to your appender layout via [MDC](http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/MDC.html).
+* Exceptions can be logged directly and are output with backtraces. Java Exceptions (i.e., NativeExceptions)
   are logged with full java backtrace(including nested exceptions).
 * Logging config for your ruby code can be added to your existing configuration. Ruby logger names are mapped to dot separated names prefixed with <tt>.jruby</tt>
 
@@ -31,7 +31,26 @@ configured(e.g. log4j.properties in the CLASSPATH). The examples should give you
     log4j.logger.jruby=info,Ruby
     log4j.logger.jruby.MyClass=debug
 
-=== Examples
+### Configuration
+
+As noted above, configuring log4j is left to the client. **You must load and configure log4j before requiring log4jruby**.
+There are multiple ways to do so. 
+In our environment, we deploy Rails apps that call and extend Java code to Tomcat as WAR files.
+We provision our app servers with ```log4j.jar``` and a ```log4j.properties``` file in in ```$TOMCAT_HOME/lib```. 
+You may also add log4j.jar and path to config file into CLASSPATH via environment variables, JAVA_OPTS, JAVA_OPTS, etc...
+Or add them into ```$CLASSPATH``` at runtime before loading log4jruby. See [examples/setup.rb](examples/setup.rb). 
+  
+Note: If you're using bundler, you can specify ```gem 'log4jruby', require: false``` in your Gemfile to delay loading the gem too early.
+  
+In a Rails application, add the following in ```config/application.rb``` or the appropriate ```config/environments``` file.
+   
+    config.logger = ActiveSupport::TaggedLogging.new(Log4jruby::Logger.get('MyApp'))
+    
+or older versions of Rails
+
+    config.logger = Log4jruby::Logger.get('MyApp')
+                           
+### Examples
 
     def foo
       logger.debug("hello from foo")
@@ -49,13 +68,9 @@ configured(e.g. log4j.properties in the CLASSPATH). The examples should give you
       examples/simple.rb:18:in `foo'
       examples/simple.rb:35:in `(root)'
 
-See more in {log4jruby/examples}[http://github.com/lenny/log4jruby/tree/master/examples/].
+See more in [log4jruby/examples](examples).
 
-=== Installation
-
-gem install log4jruby
-
-=== Usage
+### Usage
 
     class MyClass
       enable_logger
@@ -74,14 +89,6 @@ gem install log4jruby
     INFO jruby.MyModule.A my_class_method:14 - hello from class method
     INFO jruby.MyModule.A my_method:19 - hello from instance method
 
-See more in {log4jruby/examples}[http://github.com/lenny/log4jruby/tree/master/examples/].
+See more in [log4jruby/examples](examples)..
 They should be runnable from the source.
 
-=== Rails
-
-Add the following to one of your config/environment* files.
-
-   require 'log4jruby'
-   config.logger = Log4jruby::Logger.get('MyApp')
-
-You must ensure the log4j jar is required before requiring log4jruby.

data/lib/log4jruby/support/bootstrap.rb

@@ -16,3 +16,10 @@ Java::org.apache.log4j.Logger.class_eval do
     end
   end
 end
+
+# https://github.com/lenny/log4jruby/issues/14
+# https://github.com/jruby/jruby/wiki/Persistence
+if Java::org.apache.log4j.Logger.respond_to?(:__persistent__)
+  Java::org.apache.log4j.Logger.__persistent__ = true
+end
+

data/lib/log4jruby/version.rb

@@ -1,3 +1,3 @@
 module Log4jruby
-  VERSION = '2.0.0.rc3'
+  VERSION = '2.0.1'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: log4jruby
 version: !ruby/object:Gem::Version
-  version: 2.0.0.rc3
+  version: 2.0.1
 platform: java
 authors:
 - Lenny Marks
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2015-05-22 00:00:00.000000000 Z
+date: 2016-05-10 00:00:00.000000000 Z
 dependencies: []
 description: Ruby Logger using Log4j, geared toward those who use JRuby to write Ruby code using/extending Java code. Ruby and Java are configured together using traditional Log4j methods.
 email:
@@ -18,7 +18,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - CHANGELOG.md
-- README.rdoc
+- README.md
 - lib/log4jruby.rb
 - lib/log4jruby/logger.rb
 - lib/log4jruby/logger_for_class.rb
@@ -35,17 +35,17 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>'
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project:
-rubygems_version: 2.4.5
+rubygems_version: 2.4.8
 signing_key:
 specification_version: 4
 summary: Log4jruby is a thin wrapper around the Log4j Logger. It is geared more toward  those who are using JRuby to integrate with and build on top of Java code that  uses Log4j. The Log4jruby::Logger provides an interface much like the standard  ruby Logger. Your ruby loggers are given a .jruby prefix and can be configured  along with the loggers for your Java code.