-
-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Doctrine PHPCR ODM 2.0 compatibility #605
Conversation
As i can see, https://github.com/doctrine/phpcr-odm/tree/2.0 is not yet tagged (released) |
i guess you should change composer.json too |
Some slow moving vendor dependencies (like JMS Serializer, ref schmittjoh/serializer#605) hold up the development at the moment. Keeping this method for the moment will fix it. This commit should be reverted before 2.0.0 is released.
@wouterj ping |
Indeed. But as the Updated the |
Btw, cool to see some development progress in this repository again! :) |
👍 |
Thanks! Op vr 12 aug. 2016 22:04 schreef Asmir Mustafic [email protected]:
|
Some slow moving vendor dependencies (like JMS Serializer, ref schmittjoh/serializer#605) hold up the development at the moment. Keeping this method for the moment will fix it. This commit should be reverted before 2.0.0 is released.
Some slow moving vendor dependencies (like JMS Serializer, ref schmittjoh/serializer#605) hold up the development at the moment. Keeping this method for the moment will fix it. This commit should be reverted before 2.0.0 is released.
Some slow moving vendor dependencies (like JMS Serializer, ref schmittjoh/serializer#605) hold up the development at the moment. Keeping this method for the moment will fix it. This commit should be reverted before 2.0.0 is released.
Some slow moving vendor dependencies (like JMS Serializer, ref schmittjoh/serializer#605) hold up the development at the moment. Keeping this method for the moment will fix it. This commit should be reverted before 2.0.0 is released.
This available since PHPCR ODM 1.1 and the old method is removed in 2.0.