Symfony 2.1: The Doctrine bundle has moved to the Doctrine organization

January 2, 2012 · Published by

Fabien Potencier

The Symfony2 DoctrineBundle has been moved to the Doctrine organization. This allows the bundle to be maintained in a more decoupled way from Symfony for several reasons:

No coupling of release cycles anymore;
Move code to the organization that actually maintains it;
Avoid Symfony suggesting Doctrine is the only way for persistence; Symfony wants to focus on providing the View and the Controller abstraction and not make suggestions about the Model.

The Symfony standard edition has been updated to reflect this change.

In your code, you will have to change references to the Doctrine classes; for instance, the Registry class must be changed from Symfony\Bundle\DoctrineBundle\Registry to Doctrine\Bundle\DoctrineBundle\Registry.

The DoctrineFixturesBundle, DoctrineMigrationsBundle and DoctrineMongoDBBundle are now maintained in the Doctrine organization as well; however forks have been created in the Symfony repository to make all the 2.0 apps out there backwards compatible (you just need to be check that your are using the 2.0 branch).

The new repositories are here:

You can find additional information about the move on the Doctrine blog.

Published in #Living on the edge

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.

Comments

Loïc Faugeron said on Jan 2, 2012 at 18:34

This is a great move actually! No more confusion on Doctrine being the only ORM accepted by Symfony.

What about the DoctrineBridge?

Fabien Potencier Certified said on Jan 2, 2012 at 18:44

The DoctrineBridge will stay in the Symfony repository (by the way, we also have a PropelBridge now). The main point of the bridges is to ease the integration of third-party code with Symfony.

Dmitry Bykadorov said on Jan 2, 2012 at 20:23

Can I use this in my Symfony 2.0.8 project? Or more reasonable to wait for 2.1 release?

Peter Kokot said on Jan 2, 2012 at 23:10

Thank you for the notice. I admire perfect organizing that is on of the key benefits of symfony.

Jérémy Romey Certified said on Jan 3, 2012 at 08:51

Good !!! Great !!! Thanks !!!

Jérôme Forêt said on Jan 3, 2012 at 10:23

Carefull !
Symfony 2.0 is broken with last commit of SensioGeneratorBundle

Fabien Potencier Certified said on Jan 3, 2012 at 12:47

I have just created a 2.0 branch for the SensioGeneratorBundle. But if you are using the standard edition, just use the deps.lock file and you will be fine.

Clément Guillemain said on Jan 3, 2012 at 12:51

@Jérôme Forêt: it's true, losing all the morning by trying to update my vendors... by using the 2.0.8 deps file !!!

PHP Fatal error: Class 'Doctrine\Bundle\DoctrineBundle\Command\DoctrineCommand' not found in /xxxxxx/vendor/bundles/Sensio/Bundle/GeneratorBundle/Command/GenerateDoctrineCommand.php on line 18

Trying with this new deps: https://github.com/symfony/symfony-standard/blob/5dee24eb280452fe46e76f99706c21ab417462ac/deps
and this is the framework session which is broken...

Many guys have the same problem: http://groups.google.com/group/symfony2/browse_thread/thread/9a3f00cde4fe2bfd/72ab99ec44df02c3?show_docid=72ab99ec44df02c3

Clément Guillemain said on Jan 3, 2012 at 13:14

@Fabien Potencier: your solution is working, thanks ;)

Simon Mitterhofer said on Jan 3, 2012 at 14:49

#10

I've already read about the PropelBridge a couple of weeks ago and that it is allready in the master branch. I've looked into symfony 2.0.8 but i couldn't find it. In which version the PropelBridge will be available? Thanks