Closed blankse closed 7 years ago
I added an composer.lock file with twig version 1.33.2. Version 1.34 needs PHPUnit 6. The original repo has a composer.lock too.
@blankse Are you sure about that? 1.x version of Twig should work on PHPUnit 5.x, no matter which version. Only 2.x requires PHP 7.1 and PHPUnit 6.
Also, rather than adding a composer.lock
, why don't you limit the Twig constraint in composer.json
?
As for other changes, I'm vacationing today, so I'll take a look next week :)
@emodric Yes see here: https://github.com/twigphp/Twig/pull/2452 This is merged in the 1.x branch.
I can limit the twig constraint. I will change it :)
That PR means support for PHPUnit 5.4+ :) Namespaced PHPUnit classes are available since 5.4 :)
OK :) But we have version 4 ;)
Argh! You're right :)
Then Twig constraint is the way to go :) :+1:
Thanks @blankse :)
@blankse It seems there's an issue with limiting Twig to < 1.34
. Symfony as of version 2.7.29 requires Twig 1.34 and above, which conflicts with the installation of latest version eZ kernel and the version before (14.12.10) is automatically installed instead.
Is there a way to allow Twig > 1.34?
So the composer.lock for tests was not too bad ;) Otherwise we must backport this when it is finished I think: https://github.com/ezsystems/ezpublish-kernel/pull/2030
For tests, yes, but composer.lock
would not be used when installing inside of eZ Publish Community Edition, so you would still get the conflict.
Did you try using 4.8.35
version of PHPUnit which has support for namespaced TestCase
? I think that might solve your problem?
Basically, setting phpunit/phpunit
to ^4.8.35
?
We don't need the twig constraint with a composer.lock. So we would not get the conflict. I test the phpunit update: https://github.com/netgen/ezpublish-kernel/pull/55
Original Commit: https://github.com/ezsystems/ezpublish-kernel/commit/96f15b1cb893da9dc2b84fac13389d2c8195732f