Expose the HTTP status code of the failure.

[carlossg]

... so that for example 404 (not found) cannot be processed differently
from 503 (server temporarily unavailable)

[seh]

Please see the outstanding issue #5 and PR #6 for a related proposal.

[carlossg]

guess a dupe of #6

[seh]

Either approach solves the problem well enough, so I'd be happy with this one or #6. Both fix #5.

[seh]

One thing missed in a1de830 that 33e6463 took care of is removing the unnecessary "message" field in MarathonException. The base class Exception already stores the message supplied to its constructor, which MarathonException never calls now.

The question is whether to compose the message string lazily per demanded by a call to MarathonException#getMessage(), or whether to compose it at construction time and supply it to the Exception constructor. My 33e6463 proposed doing the latter.