Log Message:
Update to 2.1400
Update DEPENDS

Upstream changes:
2.1400   2014-10-31

  [BUG FIXES]

  - Moose exception classes now stringify all stack frames, to avoid issues
    in global destruction (see RT#99811)

2.1307   2014-10-26 (TRIAL RELEASE)

  [ENHANCEMENTS]

  - Support added to Moose::Exporter for exporting subs by their fully
    qualified name, as well as coderefs. This avoids internal breakage if some
    other module has monkey-patched a sub to be exported and left it anonymous
    (e.g. RT#88669). (Graham Knop)

  [BUG FIXES]

  - Further refined the overloading fixes from 2.1306, fixing fallback
    handling on older perl versions (Dave Rolsky)

2.1306   2014-10-25 (TRIAL RELEASE)

  [ENHANCEMENTS]

  - Rewrote overloading implementation to use a new Class::MOP::Overload
    object. This object properly captures all overloading information. The
    Class::MOP::Method::Overload class has been removed. (Dave Rolsky)

  [BUG FIXES]

  - If a role had method-based overloading but did not actually implement the
    specified method, its overloading was simply ignored when applying
    overloading to other roles or classes. Reported by rjbs. RT #98531.

2.1305   2014-10-22 (TRIAL RELEASE)

  [ENHANCEMENTS]

  - By default, exceptions thrown from inside Moose now remove most of the
    Moose internals from their stack trace when stringifying. This makes for
    much more readable error messages in most cases. Set the
    MOOSE_FULL_EXCEPTION env var to true to get the complete stack trace.

2.1304   2014-09-25 (TRIAL RELEASE)

  [BUG FIXES]

   - closed a memory leak in Moose exception objects where captured stack
     trace frames would contain circular references to the exception objects
     themselves (Graham Knop)

2.1303   2014-09-19 (TRIAL RELEASE)

  [TEST FIXES]

  - fix tests that fail on altered warning messages in perl 5.21.4 (RT#98987)

2.1302   2014-08-19 (TRIAL RELEASE)

  [BUG FIXES]

  - When a role consumes another role and they differ in their overloading
    fallback settings, the consuming role now silently wins instead of
    throwing an exception. This is consistent with how other
    role-consumes-role conflicts are handled.
  - Fixed the docs for overloading conflicts to match reality.

2.1301   2014-08-19 (TRIAL RELEASE)

  [BUG FIXES]

  - Conflict detection for overloading operators is now more correct. If a
    class consumed two roles that both had identical overloading methods
    (because they got them from some other role, for example), this caused an
    error, but it shouldn't. GH #4. (rjbs)
  - Similarly, when a role consumes another role, conflicts in overloading
    operators are now silently resolved in favor of the consuming role, just
    as they are with methods. Note that conflicts between the fallback setting
    for roles are still an error.

2.1300   2014-08-11 (TRIAL RELEASE)

  [ENHANCEMENTS]

  - Moose now has core support for overloading in roles. When a role with
    overloading is applied to classes or other roles, the overloading settings
    are transferred to the consumer. Conflicts between roles are treated much
    like method conflicts. This obviates the need for
    MooseX::Role::WithOverloading. If you are using
    MooseX::Role::WithOverloading, upgrade to version 0.15+ and it will simply
    become a no-op when used with this version of Moose.

  [OTHER]

  - The overloading info methods for roles and classes no longer treat
    "fallback" as an overloaded op. Instead, there are new
    get_overload_fallback_value() and set_overload_fallback_value() methods to
    deal with this explicitly. This is arguably a bug fix.