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

zend-mvc is not a conflict #15

Conversation

weierophinney
Copy link
Member

Despite #5, the classes in this package do not conflict with those in zend-mvc v2, and, in point of fact, marking this package as a conflict makes it impossible to create forwards-compatible packages that work with routing.

Despite zendframework#5, the classes in this package do not conflict with those in zend-mvc
v2, and, in point of fact, marking this package as a conflict makes it
impossible to create forwards-compatible packages that work with routing.
@weierophinney weierophinney self-assigned this Jul 6, 2016
@weierophinney weierophinney added this to the 3.0.3 milestone Jul 6, 2016
@weierophinney
Copy link
Member Author

This change may or may not be necessary.

zend-mvc v3 requires zend-router already, which means if you depend specifically on zend-mvc, you'll always have a router implementation present.

The issue will be if you want/need to depend on both. I'll leave this patch unmerged until I see there are people who require it.

@weierophinney
Copy link
Member Author

Closing; no issues reported that warrant the change at this time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant