Skip to content
This repository was archived by the owner on Jan 30, 2020. It is now read-only.

Provide forwards compatibility with servicemanager v3 #14

Conversation

weierophinney
Copy link
Member

This patch updates the develop branch to make it forwards compatible with zend-servicemanager v3 (vs only compatible), allowing a 2.6.0 version that supports both v2 and v3.

The following changes were made:

  • Removal of the zend-di dev dependency; it was literally used only for throwing an exception from a mock object. The exception was safely replaced with an SPL exception.
  • Updating of the zend-servicemanager dependency to ^2.7.5 || ^3.0.
  • Addition of the AssertionManagerCompatibilityTest, which leverages zend-servicemanager's CommonPluginManagerTrait to test both v2 and v3 compatibility of the AssertionManager implementation.
  • Updating of the AssertionManager to work under both v2 and v3:
    • Addition of $sharedByDefault + $shareByDefault
    • Addition of both validate() and validatePlugin() methods

- Removed zend-di. It's only be using for a single exception class *in a test*,
  and can be replaced with an SPL exception.
- Updated zend-servicemanager to `^2.7.5 || ^3.0`
- Updated PHP to `^5.5 || ^7.0`
- Changed dev-develop branch alias to `2.6-dev`
- As it is used in a mock, and doesn't model what would actually be
  thrown anyways.
Implements a new test, AssertionManagerCompatibilityTest, which ensures
that code works correctly for both v2 and v3.

Additionally, updates the AssertionManager to follow the current
migration guidelines.
This adds builds to the Travis matrix to allow testing both on servicemanager v2
and v3.
@weierophinney weierophinney added this to the 2.6.0 milestone Feb 2, 2016
@weierophinney weierophinney merged commit 358ba2a into zendframework:develop Feb 3, 2016
weierophinney added a commit that referenced this pull request Feb 3, 2016
@weierophinney weierophinney deleted the feature/servicemanager-forwards-compat branch February 3, 2016 20:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant