summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristian Flothmann <christian.flothmann@xabbuh.de>2015-10-06 14:38:55 +0200
committerChristian Flothmann <christian.flothmann@xabbuh.de>2015-10-27 21:57:16 +0100
commitd87c38213e72fd3d8068be466ac654e0c13cdb2d (patch)
tree72c7439db9122d1900e78bae7a0bd0c9efd695a4
parenta23e3f65689331b054159daf8316cc3da3676596 (diff)
downloadsymfony-security-d87c38213e72fd3d8068be466ac654e0c13cdb2d.zip
symfony-security-d87c38213e72fd3d8068be466ac654e0c13cdb2d.tar.gz
symfony-security-d87c38213e72fd3d8068be466ac654e0c13cdb2d.tar.bz2
don't allow to install the split Security packages
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.
-rw-r--r--composer.json5
1 files changed, 5 insertions, 0 deletions
diff --git a/composer.json b/composer.json
index 2026fc4..4c2b070 100644
--- a/composer.json
+++ b/composer.json
@@ -32,6 +32,11 @@
"psr/log": "~1.0",
"ircmaxell/password-compat": "~1.0"
},
+ "replace": {
+ "symfony/security-acl": "self.version",
+ "symfony/security-core": "self.version",
+ "symfony/security-http": "self.version"
+ },
"suggest": {
"symfony/class-loader": "",
"symfony/finder": "",