Don_Busi
2015-04-11 20:37:00 UTC
Hi everybody,
I have the same problem as in this thread on stackoverflow:
http://stackoverflow.com/questions/28850809/disable-deprecated-warning-in-symfony-2-7
Some of the bundles I open-sourced ARE compatible with Symfony version 2.1
through 2.7.
But in 2.7 there is deprecated code being used at several places..... it
still works fine, but errors are being thrown during unit-tests.
Now as suggested in the stackoverflow-thread mentioned above, I could
change the default-error reporting in the AppKernel in my development
environment. But on travis-ci the packages still appear faild for Symfony
2.7.
I mean the bundle works fine with Symfony 2.7, to use it with Symfony 3.0
I'll need to remove all the deprecations, but Symfony 3.0 will only be
released in November, so I'll release a new version to be used with Symfony
3.0 then.
What do you do with your bundles? Just limit Symfony to ">=2.1,<2.7" in
your .travis-file or is there an other workaround?
Cheers,
Don
--
--
If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "Symfony2" group.
To post to this group, send email to ***@googlegroups.com
To unsubscribe from this group, send email to
symfony2+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony2?hl=en
---
You received this message because you are subscribed to the Google Groups "Symfony2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to symfony2+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I have the same problem as in this thread on stackoverflow:
http://stackoverflow.com/questions/28850809/disable-deprecated-warning-in-symfony-2-7
Some of the bundles I open-sourced ARE compatible with Symfony version 2.1
through 2.7.
But in 2.7 there is deprecated code being used at several places..... it
still works fine, but errors are being thrown during unit-tests.
Now as suggested in the stackoverflow-thread mentioned above, I could
change the default-error reporting in the AppKernel in my development
environment. But on travis-ci the packages still appear faild for Symfony
2.7.
I mean the bundle works fine with Symfony 2.7, to use it with Symfony 3.0
I'll need to remove all the deprecations, but Symfony 3.0 will only be
released in November, so I'll release a new version to be used with Symfony
3.0 then.
What do you do with your bundles? Just limit Symfony to ">=2.1,<2.7" in
your .travis-file or is there an other workaround?
Cheers,
Don
--
--
If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "Symfony2" group.
To post to this group, send email to ***@googlegroups.com
To unsubscribe from this group, send email to
symfony2+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony2?hl=en
---
You received this message because you are subscribed to the Google Groups "Symfony2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to symfony2+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.