symfony-cmf / standard-edition

The "Symfony CMF Standard Edition" distribution
cmf.symfony.com
MIT License
118 stars 48 forks source link

Composer issue from fresh install #66

Open ghost opened 7 years ago

ghost commented 7 years ago

My composer.json is currupted, its a fresh install of your standard edition:

"require": {
    "php": "^5.6|^7.0",
    "symfony/symfony": "^3.2",
    "doctrine/orm": "^2.5",
    "doctrine/doctrine-bundle": "^1.6",
    "doctrine/data-fixtures": "^1.2",
    "doctrine/doctrine-cache-bundle": "^1.2",
    "symfony/swiftmailer-bundle": "^2.3.10",
    "symfony/monolog-bundle": "^3.0.2",
    "symfony/polyfill-apcu": "^1.0",
    "sensio/distribution-bundle": "^5.0",
    "sensio/framework-extra-bundle": "^3.0.2",
    "symfony-cmf/symfony-cmf": "2.0.*",
    "jackalope/jackalope-doctrine-dbal": "~1.1",
    "symfony-cmf/menu-bundle": "^2.1",
    "sonata-project/doctrine-phpcr-admin-bundle": "^1.2",
    "symfony-cmf/tree-browser-bundle": "^1.2",
    "symfony-cmf/routing-bundle": "^2.0"
},

Notice how there is no routing auto bundle, when i attempt to composer update i get this:

Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages.

Problem 1

ghost commented 7 years ago

I followed the default tutorial, here: http://symfony.com/doc/master/cmf/tutorial/getting-started.html, 2.1 master

ghost commented 7 years ago

I attempted to mimic the exact composer.json that you present here, it results in:

Using version ^1.1 for symfony-cmf/routing-auto-bundle ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages.

Problem 1

Installation failed, reverting ./composer.json to its original content.

dbu commented 7 years ago

the problem is that your composer.json requires symfony 3.2. we are in the process of tagging stable versions of the cmf bundles that support symfony 3. tree browser is not yet released as version 2. and i think symfony-cmf/symfony-cmf 2.0 has also not been tagged as stable yet

you either need to use symfony 2.8 or allow unstable dependencies (until we tagged all tree browser related things)

ghost commented 7 years ago

Hi dbu, thanks for the fast response, my composer.json is at:

"minimum-stability": "dev",
"prefer-stable": true

How can i further allow unstable dependencies?

dbu commented 7 years ago

hm, ok then that does not help. looking at the state vomit from composer, it might be the sonata admin. https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/blob/1.x/composer.json says that only symfony 2 is supported. master of sonata would be ^2.0

but sonata admin is the part that is really not quite there yet. we appreciate help cleaning up things if you want (wouter knows that part best but he is on holidays this week) - just be warned that if you use master of that, plus the new symfony-cmf/sonata-phpcr-admin-integration-bundle things could still be a bit wobbly for a while.

ghost commented 7 years ago

Hmm, i am considering Symfony-CMF for a enterprise project I am beginning, with a short deadline, I would love to help clean it up, but I don't think I can make the deadline doing that, since I am not familiar with the framework at all, best bet would probably be to try the Symfony2 version.

dbu commented 7 years ago

upgrading from symfony 2.8 to 3 should be relatively easy. for the cmf part, the only part that likely will generate some effort would be the sonata admins, if you use them to build an admin.