symfony/security from 2.3 and symfony/security-core conflict #16134
Labels
Comments
This was referenced Oct 5, 2015
fabpot
added a commit
that referenced
this issue
Oct 28, 2015
…ges (xabbuh) This PR was merged into the 2.3 branch. Discussion ---------- [Security] don't allow to install the split Security packages | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #16134 | License | MIT | Doc PR | Currently, you would be able to install the Security component fromm Symfony 2.3 together with one of the split packages from a higher Symfony vesion like this: ```json { "require": { "symfony/symfony": "2.3.*", "symfony/security-core": "~2.7" } } ``` However, you will end up with classes being present twice. This must be reverted after merging up in the `2.7` branch. Commits ------- 0d14064 don't allow to install the split Security packages
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, you could install the Security component in version 2.3 while also requiring the
symfony/security-corepackage from more recent Symfony versions like this:{ "require": { "symfony/symfony": "2.3.*", "symfony/security-core": "~2.7" } }The installation will succeed, but you will end up with duplicated classes. Is there anything we can do here? For example, what about adding conflict rules in the Security component's
composer.jsonfile in2.3?The text was updated successfully, but these errors were encountered: