v3.4.6

• Swallow Throwables thrown when configuring bugsnag appender
  #140

v3.4.5

• Migrate non-standard device fields to metaData.device
  #131

• Set thread name to aid debugging
  #138

• Merge internal checkstyle rules
  #137

v3.4.4

• Remove unnecessary @Configuration annotation
  #130

v3.4.3

• Support other methods of configuring a TaskScheduler when setting ErrorHandler on scheduled tasks
  #126

v3.4.2

• Ensure session counts are thread safe
  #122

• Prevent application hangs due to session flushing
  #121

v3.4.0

• Enhanced support for Spring applications with the new bugsnag-spring notifier
• The ability to report throwables to Bugsnag with the logback appender BugsnagAppender

Two artifacts are now available for this platform:

• bugsnag-java - intended for plain Java applications
• bugsnag-spring - provides enhanced support for Spring applications

It is recommended that you migrate to bugsnag-spring if you develop a Spring application, as it enhances the quantity and quality of error reports which are sent automatically. Full upgrade instructions can be found here.

No upgrade steps are required for bugsnag-java in this release.

• Added BugsnagAppender that can report throwables from existing log statements to Bugsnag, using logback
• [Spring] Automatically report exceptions thrown when processing MVC/REST requests
• [Spring] Automatically report exceptions thrown in scheduled tasks
• [Spring] Added BugsnagAsyncConfig class to simplify capture of uncaught exceptions in async tasks
• [Spring] Automatically attach request metadata to reports
• [Spring] Automatically attach Spring version information to reports
• [Spring] Automatically track sessions for each MVC request

See UPGRADING for upgrade details and the docs for further information on new functionality.

v3.3.0

• Capture trace of error reporting thread and identify with boolean flag
  #87

v3.2.1

• Add null check when disconnecting HttpUrlConnection
  #92

• Make constructors public for SyncHttpDelivery
  #97

v3.2.0

This release introduces automatic tracking of sessions, which by
default are captured for each HTTP request received via the Servlet API. To disable this data collection, call bugsnag.setAutoCaptureSessions(false).

If you wish to use a custom strategy for tracking sessions, call bugsnag.startSession() in the
appropriate place within your application.
Jamie Lynch
#70

Deprecation notice: setEndpoints(String notify, String session) is now the preferred way to configure custom endpoints,
if you are using Bugsnag On-Premise.

v3.2.0-beta

Important: This is a beta release which introduces automatic tracking of sessions, which by
default are captured for each HTTP request received via the Servlet API
To disable this data collection, call bugsnag.setAutoCaptureSessions(false).
If you wish to use a custom strategy for tracking sessions, call bugsnag.startSession() in the
appropriate place within your application.
Jamie Lynch
#70

Deprecation notice
setEndpoints(String notify, String session) is now the preferred way to configure custom endpoints,
if you are using Bugsnag On-Premise.