added dependency to rsolr for Solr output
Update logstash.spec
Update logstash.spec

Removed the disabled java, should be enabled again.
Update logstash.spec

* Added a source5 with a default logstash.conf since logstash does not start without a config.

* Added buildarch so it can be build on i386
Update logstash.init

Fixed the init.d script.

Example taken from: https://github.com/mhorbul/logstash-rpm/
Update logstash.sysconfig

Taken from: https://github.com/mhorbul/logstash-rpm/tree/master/SOURCES
Create logstash.wrapper

Fixed the problem with the plugins as this no longer works.

Original file taken from:
https://github.com/piojo/logstash-rpm/blob/lsb/SOURCES/logstash.wrapper
Create logstash.conf

Added a default "Logstash.conf" as example and so logstash can actually run once you compile the rpm.
Added optional username and password to elasticsearch_http output plugin. Fixes LOGSTASH-902.
Setup a periodic filter flush thread.

This got lost in 9542246 and unbreaks LOGSTASH-1284.
Update graphite.rb

minor spelling correction
Adding note about outputs/elasticsearch/index requiring lowercase letters

ElasticSearch will refuse to create (without an error) any indexes that contain uppercase letters. Lowercase letters, numbers, and punctuation are permitted.
Fix memory leak in syslog input. (tcp server)

Remove the client from the clients list when the connection is closed.
Add elapsed filter
Further validate date filter within register method
since the plugin's name changed to collate, update the comments and method name, vars to collate, to keep consistent
Break out json into json_lines so that users streaming json can use the line delimited codec and users using message based transports i.e. redis can still use a codec without requiring the message end in '\n'
Add more descriptive docs for json/json_lines codecs
Allow output plugins to declare that, for a given configuration, workers are
not supported. Such reasons could include inability to share a resource
(like a listening socket, etc). This declaration will force a
single-worker setting and allow logstash to warn the user instead of
aborting.
Try to fix any @timestamp values if someone mucks with that field value
and turns it into a string through the json filter.