@message was missing in event, added 'Message' field to @message.
- make 'target' an absolute path otherwise ruby 2.0.0+rubygems 2.x
  refuses to install things. Cute :(
- Disable doc generation on rubygems 2
- Try to set GEM_HOME/GEM_PATH early on in the process.
- make RUBYVER tunable for ruby 2.0, not that it works well yet.
- fix backwards compat
- update readme
LOGSTASH-1003 LOGSTASH-1038 fixing both issues in one commit because the rabbitmq input is functionally broken until both are fixed
Fix validation so they will work.
Merge pull request #461 from electrical/fix_validation

Fix validation so they will work.
- make these proper tests that run in a way that rspec understands.
- add more-documented sysconfig defaults for centos
default quiet specs
Start hacking on kibana integration
- add more log flags
Added message_format attribute to nagios_nsca output
Made documentation consistent with other outputs that provide message_format such as pipe.
Added more information for building from git

Added make vendor-elasticsearch for getting jars out of elasticsearch for running from git.
Merge pull request #463 from timconradinc/patch-2

Added more information for building from git
Merge pull request #459 from jkoppe/jkoppe-bunny-rabbitmq-fixes

Fixing both LOGSTASH-1003 and LOGSTASH-1038
- use RbConfig for platform detection now.
- File.expand_path("/....") on windows platform returns "C:/...." which
is expected but not in our monkeypatching to work around other bugs.

  This should resolve logstash's known windows 'file input' problems and
  whatnot. I've tested this on a Windows Server 2012 EC2 instance
  provided by the Alex Corley at Zenoss <3

  Test config showed file inputs working. I was able to watch
  "C:\test.log" and edit the file with notepad, adding lines, and
  logstash would see new events show up when I saved.