log4r-color 1.2 → 1.2.2

data/README.textile

@@ -0,0 +1,143 @@
+h1. A flexible logging library for Ruby, now in color
+
+This project is currently decoupled from the main _log4r_ project which it rests on. 
+The main addition to log4r in this project is the _ColorOutputter_ which uses "colorize":https://github.com/fazibear/colorize to display logs in the console/terminal with colorschemes for each log level to make it easy to distinquish them.
+
+This project is used in "logging_assist":https://github.com/kristianmandrup/logging_assist which wraps log4r-color in a convenient DSL syntax.
+
+h2. Release
+
+This release:      *1.2*
+Release date:      *Jan/2011*
+License:           LGPLv3
+
+h2. Contributors      
+
+* Colby Gutierrez-Kraybill
+* Kristian Mandrup (ColorOutputter)
+* Leon Torres - Original Maintainer
+* Martain Stannard - RollingFileOutputter
+* Steve Lumos - SyslogOutputter
+* Mark Lewandowski - ScribeOutputter
+* Andreas Hund - YamlConfigurator
+* Jamis Buck - log4r.gemspec
+* Charles Strahan - log4jxml/chainsaw integration
+* Nitay Joffe - STARTTLS
+* David Siegal - Smart updates to RollingFileOutputter
+
+"Homepage":http://log4r.rubyforge.org/
+"Download":http://rubyforge.org/frs/?group_id=203
+
+h2. Summary
+
+Log4r is a comprehensive and flexible logging library written in Ruby for use 
+in Ruby programs. It features a hierarchical logging system of any number of 
+levels, custom level names, logger inheritance, multiple output destinations 
+per log event, execution tracing, custom formatting, thread safteyness, XML 
+and YAML configuration, and more.
+
+
+h2. Requirements
+
+* (required) Ruby >= 1.7.0 (use log4r 1.0.2 for Ruby 1.6)
+* (optional) RubyGems for installing Log4r as a gem
+* (optional) Ruby syslog library for SyslogOutputter
+* (optional) XML configuration requires REXML
+* (optional) log4j chainsaw integration requires 'builder' >= 2.0
+* (optional) STARTTLS email login, requires 'smtp_tls" if Ruby <= 1.8.6
+
+h3. Gem requirements
+
+* colorize
+* scribe
+
+h2. Install
+
+<code>gem install log4r-color</code>
+
+h2. Usage
+
+Here is an example of setting up a logger with ColorOutputter using a color scheme. While logging, one of the color schemes is changed and it applies immediately to log messages after. 
+
+<pre>require 'log4r-color'
+include Log4r
+
+Logger.global.level = ALL
+formatter = PatternFormatter.new(:pattern => "%l - %m - %c")
+
+ColorOutputter.new 'color', {:colors => 
+  { 
+    :debug  => :light_blue, 
+    :info   => :light_blue, 
+    :warn   => :yellow, 
+    :error  => :red, 
+    :fatal  => {:color => :red, :background => :white} 
+  } 
+}
+
+Logger.new('color_logger', DEBUG).add('color')
+
+def do_logging(log)
+  puts "--"
+  log.debug "This is debug"
+  log.info "This is info"
+  log.warn "This is warn"
+  Outputter['color'].colors[:info] = :green
+  log.info "This is info again, now in green"
+  log.error "This is error"
+  log.fatal "This is fatal"  
+end
+
+do_logging Logger['color_logger']  
+
+Note: You can set the log levels you allow via the `Log4r.LNAMES` constant, by default set to `['ALL']` to allow any log level.
+
+</pre>
+
+h2. More Info
+
+* Installation instructions are in the file INSTALL
+
+* Comprehensive examples are provided in examples/ and can be run right away
+
+* Log4r homepage: doc/index.html
+  Online: http://log4r.rubyforge.org/
+
+* Manual: doc/manual.html
+  Online: http://log4r.rubyforge.org/manual.html
+  
+* RDoc API reference: doc/rdoc/index.html 
+  Online: http://log4r.rubyforge.org/rdoc/index.html
+  
+* The changelog
+
+* Log4r is hosted by RubyForge, which provides news, bug tracking and a forum
+
+* Feel free to bug the maintainer with any questions (listed at top of file)
+
+
+h2. Usability
+
+Log4r works really well, so please take advantage of it right away! :)
+All versions since 0.9.2 have been stable and backward-compatible. The
+code is stable enough that updates are infrequent and usually only for
+adding features or keeping the code up to date with Ruby.
+
+
+h2. Platform Issues
+
+Log4r is known to work on Linux and WindowsXP. It's safe to assume that Log4r 
+will work on any Ruby-supported platform.
+
+
+h2. When Trouble Strikes
+
+Log4r comes with an internal logger. To see its output, create a logger
+named 'log4r' before any others and give it a suitable outputter,
+
+<pre>
+  trouble = Logger.new['log4r']
+  trouble.add Outputter.stdout  
+</pre>
+
+

data/Rakefile

@@ -10,7 +10,7 @@ require 'date'
 require 'fileutils'
 
 GEM = "log4r-color"
-GEM_VERSION = "1.2"
+GEM_VERSION = "1.2.2"
 AUTHORS = "Colby Gutierrez-Kraybill, Kristian Mandrup (color outputter)"
 EMAIL = "colby@astro.berkeley.edu, kmandrup@gmail.com"
 HOMEPAGE = %q{http://log4r.rubyforge.org}

data/doc/content/manual.html

@@ -206,7 +206,7 @@ destinations as well as its own. This behavior is optional, but allows one
 to structure a powerful, and easily configurable logging system.
 <p/>
 To find out more about loggers, please see
-<a href="rdoc/files/log4r/logger_rb.html">rdoc/files/log4r/logger_rb.html</a>.
+<a href="rdoc/files/log4r-color/logger_rb.html">rdoc/files/log4r-color/logger_rb.html</a>.
 <p><hr noshade color="#AA0000">
 <a name="outputters">
 <h4 ><a href="#toc">Outputters</a></h4>
@@ -227,8 +227,8 @@ extending log4r outputters, the well documented code and the open source
 license.
 <p/>
 To find out more about outputters, please see
-<a href="rdoc/files/log4r/outputter/outputter_rb.html">
-rdoc/files/log4r/outputter/outputter_rb.html</a>.
+<a href="rdoc/files/log4r-color/outputter/outputter_rb.html">
+rdoc/files/log4r-color/outputter/outputter_rb.html</a>.
 <p><hr noshade color="#AA0000">
 <a name="formatters">
 <h4 ><a href="#toc">Formatters</a></h4>
@@ -238,12 +238,12 @@ PatternFormatter uses sprintf-like directives to format log messages and
 eliminates the need for custom Formatters.
 <p/>
 To find out more about formatters, please see
-<a href="rdoc/files/log4r/formatter/formatter_rb.html">
-rdoc/files/log4r/formatter/formatter_rb.html</a>.
+<a href="rdoc/files/log4r-color/formatter/formatter_rb.html">
+rdoc/files/log4r-color/formatter/formatter_rb.html</a>.
 <br/>
 To find out more about PatternFormatter, please see
-<a href="rdoc/files/log4r/formatter/patternformatter_rb.html">
-rdoc/files/log4r/formatter/patternformatter_rb.html</a>.
+<a href="rdoc/files/log4r-color/formatter/patternformatter_rb.html">
+rdoc/files/log4r-color/formatter/patternformatter_rb.html</a>.
 <p><hr noshade color="#AA0000">
 <a name="config">
 <h4 ><a href="#toc">Configuration</a></h4>
@@ -256,10 +256,10 @@ be configured without needing to write extra code. This is acomplished by
 taking advantage of Ruby's powerful reflection capabilities.
 <p/>
 To find out more about configuration, please see
-<a href="rdoc/files/log4r/configurator_rb.html">rdoc/files/log4r/configurator_rb.html</a>.
+<a href="rdoc/files/log4r-color/configurator_rb.html">rdoc/files/log4r-color/configurator_rb.html</a>.
 <br/>
 For YAML configuration, also see
-<a href="rdoc/files/log4r/yamlconfigurator_rb.html">rdoc/files/log4r/yamlconfigurator.html</a>
+<a href="rdoc/files/log4r-color/yamlconfigurator_rb.html">rdoc/files/log4r-color/yamlconfigurator.html</a>
 
 <p><hr noshade color="#AA0000">
 <a name="remote">
@@ -270,8 +270,8 @@ This is accomplished using the distributed Ruby library ROMP, a subclass of
 Logger called LogServer, and a RemoteOutputter.
 <p/>
 To find out more about remote logging, please see
-<a href="rdoc/files/log4r/logserver_rb.html">
-rdoc/files/log4r/logserver_rb.html</a>
+<a href="rdoc/files/log4r-color/logserver_rb.html">
+rdoc/files/log4r-color/logserver_rb.html</a>
 <p/>
 Alternatively, one can just send log reports via email using EmailOutputter.
 <p/>

data/doc/dev/README.developers

@@ -10,7 +10,7 @@ Project Full Name:  Log4r
 Project Unix Name:  log4r
 CVS Server:         cvs.log4r.rubyforge.org
 Shell/Web Server:   log4r.rubyforge.org
-Path to web pages:  /var/www/gforge-projects/log4r/
+Path to web pages:  /var/www/gforge-projects/log4r-color/
 
 
 HTML manual and site

data/doc/templates/main.html

@@ -27,7 +27,7 @@
 <tr><td><a href="http://sourceforge.net/project/showfiles.php?group_id=43396">
 Download</a></td></tr>
 <tr><td nowrap="true">
-    <a href="http://rubyforge.org/projects/log4r/">@ RubyForge</a>
+    <a href="http://rubyforge.org/projects/log4r-color/">@ RubyForge</a>
 </td></tr>
 <tr><td>
 <a href="license.html">License</a>

data/lib/log4r-color/base.rb

@@ -56,16 +56,16 @@ module Log4r
       raise ArgumentError, "Colors option must consist of a hash where each key is the log level to define a color scheme for" if !colors.kind_of? Hash
       invalid_levels = colors.keys.reject {|level| valid_levels.include? level}
       if !invalid_levels.empty?
-        raise ArgumentError, "Color schemes can not be defined for these invalid log levels: #{invalid_levels.join(', ')}"
+        raise ArgumentError, "Color schemes cannot be defined for these invalid log levels: #{invalid_levels.join(', ')}"
       end
     end
 
     def self.level_key level 
-      valid_levels[level -1]
+      valid_levels[level]
     end
 
     def self.valid_levels
-      [:debug, :info, :warn, :error, :fatal]
+      LNAMES.collect { |level| level.downcase.to_sym }
     end
   
     # Shortcut for decoding 'true', 'false', true, false or nil into a bool

data/lib/log4r-color/outputter/emailoutputter.rb

@@ -95,7 +95,7 @@ module Log4r
       ### build a mail header for RFC 822
       rfc822msg =
         "From: #{@from}\n" +
-        "To: #{@to}\n" +
+        "To: #{@to.join(', ')}\n" +
         "Subject: #{@subject}\n" +
         "Date: #{Time.now.strftime( "%a, %d %b %Y %H:%M:%S %z %Z")}\n" +
         "Message-Id: <#{"%.8f" % Time.now.to_f}@#{@domain}>\n\n" +

metadata

@@ -1,61 +1,60 @@
---- !ruby/object:Gem::Specification 
+--- !ruby/object:Gem::Specification
 name: log4r-color
-version: !ruby/object:Gem::Version 
-  prerelease: false
-  segments: 
-  - 1
-  - 2
-  version: "1.2"
+version: !ruby/object:Gem::Version
+  version: 1.2.2
+  prerelease: 
 platform: ruby
-authors: 
+authors:
 - Colby Gutierrez-Kraybill, Kristian Mandrup (color outputter)
 autorequire: 
 bindir: bin
 cert_chain: []
-
-date: 2011-01-09 00:00:00 +01:00
-default_executable: 
-dependencies: 
-- !ruby/object:Gem::Dependency 
+date: 2012-09-09 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
   name: scribe
-  prerelease: false
-  requirement: &id001 !ruby/object:Gem::Requirement 
+  requirement: !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        segments: 
-        - 0
-        version: "0"
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
   type: :runtime
-  version_requirements: *id001
-- !ruby/object:Gem::Dependency 
-  name: colorize
   prerelease: false
-  requirement: &id002 !ruby/object:Gem::Requirement 
+  version_requirements: !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        segments: 
-        - 0
-        version: "0"
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: colorize
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
   type: :runtime
-  version_requirements: *id002
-description: "See also: http://logging.apache.org/log4j"
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+description: ! 'See also: http://logging.apache.org/log4j'
 email: colby@astro.berkeley.edu, kmandrup@gmail.com
 executables: []
-
 extensions: []
-
-extra_rdoc_files: 
-- README
+extra_rdoc_files:
+- README.textile
 - LICENSE
 - TODO
-files: 
+files:
 - LICENSE
 - LICENSE.LGPLv3
-- README
+- README.textile
 - INSTALL
 - Rakefile
 - TODO
@@ -158,37 +157,29 @@ files:
 - tests/testpatternformatter.rb
 - tests/testthreads.rb
 - tests/testxmlconf.rb
-has_rdoc: true
 homepage: http://log4r.rubyforge.org
 licenses: []
-
 post_install_message: 
 rdoc_options: []
-
-require_paths: 
+require_paths:
 - lib
-required_ruby_version: !ruby/object:Gem::Requirement 
+required_ruby_version: !ruby/object:Gem::Requirement
   none: false
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      segments: 
-      - 0
-      version: "0"
-required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      segments: 
-      - 0
-      version: "0"
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
 requirements: []
-
 rubyforge_project: log4r-color
-rubygems_version: 1.3.7
+rubygems_version: 1.8.24
 signing_key: 
 specification_version: 3
 summary: Log4r, logging framework for ruby
 test_files: []
-
+has_rdoc: 

data/README

@@ -1,95 +0,0 @@
-Log4r - A flexible logging library for Ruby
-
-
-This release:      1.1.9 - ALPHA
-Release date:      XX/Jun/2010
-License:           LGPLv3
-Maintainer:        Colby Gutierrez-Kraybill
-Contributors:      Leon Torres               Original Maintainer
-                   Martain Stannard          RollingFileOutputter
-                   Steve Lumos               SyslogOutputter
-                   Mark Lewandowski          ScribeOutputter
-                   Andreas Hund              YamlConfigurator
-                   Jamis Buck                log4r.gemspec
-                   Charles Strahan           log4jxml/chainsaw integration
-                   Nitay Joffe               STARTTLS
-                   David Siegal              Smart updates to RollingFileOutputter
-Homepage:          http://log4r.rubyforge.org/
-Download:          http://rubyforge.org/frs/?group_id=203
-
-Summary
--------
-
-Log4r is a comprehensive and flexible logging library written in Ruby for use 
-in Ruby programs. It features a hierarchical logging system of any number of 
-levels, custom level names, logger inheritance, multiple output destinations 
-per log event, execution tracing, custom formatting, thread safteyness, XML 
-and YAML configuration, and more.
-
-
-Requirements
-------------
-
-* (required) Ruby >= 1.7.0 (use log4r 1.0.2 for Ruby 1.6)
-* (optional) RubyGems for installing Log4r as a gem
-* (optional) Ruby syslog library for SyslogOutputter
-* (optional) XML configuration requires REXML
-* (optional) log4j chainsaw integration requires 'builder' >= 2.0
-* (optional) STARTTLS email login, requires 'smtp_tls" if Ruby <= 1.8.6
-
-
-More Info
----------
-
-* Installation instructions are in the file INSTALL
-
-* Comprehensive examples are provided in examples/ and can be run right away
-
-* Log4r homepage: doc/index.html
-  Online: http://log4r.rubyforge.org/
-
-* Manual: doc/manual.html
-  Online: http://log4r.rubyforge.org/manual.html
-  
-* RDoc API reference: doc/rdoc/index.html 
-  Online: http://log4r.rubyforge.org/rdoc/index.html
-  
-* The changelog
-
-* Log4r is hosted by RubyForge, which provides news, bug tracking and a forum
-
-* Feel free to bug the maintainer with any questions (listed at top of file)
-
-
-Usability
----------
-
-Log4r works really well, so please take advantage of it right away! :)
-All versions since 0.9.2 have been stable and backward-compatible. The
-code is stable enough that updates are infrequent and usually only for
-adding features or keeping the code up to date with Ruby.
-
-
-Platform Issues
----------------
-
-Log4r is known to work on Linux and WindowsXP. It's safe to assume that Log4r 
-will work on any Ruby-supported platform.
-
-
-When Trouble Strikes
---------------------
-
-Log4r comes with an internal logger. To see its output, create a logger
-named 'log4r' before any others and give it a suitable outputter,
-
-  trouble = Logger.new['log4r']
-  trouble.add Outputter.stdout
-
-Try running the unit tests provided (run the file tests/runtest.rb). Let
-the maintainer know what's up and feel free to explore and fix the 
-code yourself. It's well documented and written in Ruby. :)
-
-Also, try out the bug/request tracking system at 
-http://rubyforge.org/tracker/?group_id=203
-