-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LatestCommand Issue #91
Comments
since this was integrated in migrations, I think you should stick to |
We should register the command only when the LatestCommand command is available. You can look at DoctrineBundle or DoctrinePHPCRBundle for such cases |
It is on dev-master although it broke when composer updated to bf9bcb3. Seems like I can get it working by adding "doctrine/migrations": "1.0.x-dev", to my composer file. I think the requirement should be updated to a version of doctrine/migrations which has the LatestCommand file or Stof's suggestion. |
@github-scott if you don't allow dev versions of |
The same here. Because the bundle require |
do you have |
I have "minimum-stability": "alpha" in the composer file so I assume this is causing the problem for me. |
well, as I said, you have to whitelist the dev version of doctrine/migrations for now. |
I've
Indeed adding |
Well, the culprit is indeed |
Me also got an old version, same issue. |
Closing as it's old and probably fixed by that commit 0a3c377 |
I can confirm that below config works:
|
Since this commit - bf9bcb3
I now get this error:-
PHP Fatal error: Class 'Doctrine\DBAL\Migrations\Tools\Console\Command\LatestCommand' not found in /...../vendor/doctrine/doctrine-migrations-bundle/Doctrine/Bundle/MigrationsBundle/Command/MigrationsLatestDoctrineCommand.php on line 30
Is there a dependancy required to make sure Doctrine\DBAL\Migrations\Tools\Console\Command\LatestCommand exists?
The text was updated successfully, but these errors were encountered: