Add option to disable sending module info

Users can now opt-out of automatically sending this data by setting the
config attribute `send_modules` to `false`.

In projects which version their dependencies using a Gemfile, sending
the list of loaded modules may not provide much value. In particular, if
you send a parameter including what version of the application is
running, we can inspect the Gemfile.lock for all this data, and don't
need it to appear in every sentry instance.
Pass Event.capture_exception configuration into Event instances

If capture_exception is using a customized configuration, that config
should be passed into Event instances that are created by it.

Change-Id: I8b3a04b33a611c68d8960f3464496a3172569694
Reviewed-on: https://gerrit.causes.com/9014
Reviewed-by: Joe Lencioni <joe.lencioni@causes.com>
Tested-by: Noah Silas <noah@causes.com>
Merge pull request #13 from causes/pull-requests/optional_module_info

Add option to disable sending module info
Refactoring Raven::Event.capture_exception

It would be great to be able to Subclass Raven::Event to add custom
behavior for things like stack trace sanitization. Before we can do
that, it would be helpful to have smaller functions that to override. I
have split up Raven::Event.capture_exception to allow higher granularity
in overriding behaviour.

I also have added some limited specs to help ensure that the new
behavior matches the old. The only significant change in behaviour is
that before the refactor, passing an exception that did not have a
backtrace would raise an exception, which was making testing difficult
and prevented some types of logging (for instance, passing in an
exception that was constructed, rather than thrown). I added a guard
around the backtrace parsing to prevent this failure mode.
Only send module version strings

If ActiveSupport has been loaded, it overrides the way that a
Gem::Specification is JSONified, causing it to send a very verbose
hash. Casting the Gem::Specification object to a string first will
send a simple version string (like '1.2.3') in either case.

Fixes #15
Add basic init file for certain Rails 3 versions
Exceptional seems to know Rails better than we do, so lets assume theres some unknown magic where we need ./init.rb
Revert "Exceptional seems to know Rails better than we do, so lets assume theres some unknown magic where we need ./init.rb"

This reverts commit b31d7f082c17825f6cece86fbd686c230c7f474b.
Revert "Add basic init file for certain Rails 3 versions"

This reverts commit 386e1e823f4206b8f05593118d9b6de13166db7e.
Add actual exception example to Raven.capture block style
Bump master version.
Cleanup module sending a tad.
Use multi_json instead of yajl-ruby

This will make sentry-raven compatible with jruby and others json
implementations.
Merge pull request #20 from sobrinho/master

Use multi_json instead of yajl-ruby
manually initialize interface defaults to avoid hashie bug https://github.com/intridea/hashie/issues/53
Merge pull request #21 from msaffitz/master

Avoid Hashie Dash Bug with Parameter Defaults leading to erroneous headers, env in Sentry events
Don't send "404 Page Not Found" messages

ActiveRecord::RecordNotFound and ActionController::RoutingError will result in 404 pages, which are legitimate exceptions in Rails
Exclude 404 from Rails DebugExceptionsCatcher
Log exception
Compare by name