-
Notifications
You must be signed in to change notification settings - Fork 90
[dev-develop] using zend-servicemanager v3 got error: ": Unable to resolve service "application" to a factory" #78
Comments
I'll look into this first thing today! One note: you don't need to add the entries for zend-servicemanager and zend-eventmanager; the develop branch of zend-mvc pins to stable versions of all components. I'd instead use this: "zendframework/zend-mvc": "dev-develop as 2.7.0" which will bring it in as a stable version, and use the latest stable version of any dependencies it has. If you want to force usage of zend-servicemanager v3 and/or zend-eventmanager v3, add the following as well: "zendframework/zend-stdlib": "^3.0",
"zendframework/zend-eventmanager": "^3.0",
"zendframework/zend-servicemanager": "^3.0.3",
"zendframework/zend-hydrator": "^2.1", With regards to your issue, I'm pretty sure it's just a missing alias, which should be something I can resolve easily; thanks for the report! |
@samsonasik I've done the following
From there, I browsed to localhost:8080... and all worked fine. Packages installed (minus dev stuff from PHPunit) are:
Can you give more details on how to recreate the issue you observed? |
It is working fine by just use zend-mvc:dev-develop, The issue is raised when I added zend-servicemanager ^3.0 and Zend-eventmanager ^3.0 Warm regards, Abdul Malik Ikhsan Pada 29 Feb 2016, pukul 21.45, weierophinney notifications@github.com menulis:
|
Okay, will try that as well; thanks for the clarification, @samsonasik ! |
@weierophinney I've created PR for it #80 |
Fixes zendframework#78 : using uppercase for 'Application' service
This is the error:
My composer.json:
The text was updated successfully, but these errors were encountered: