Symfony 2.1.2 released
September 20, 2012 • Published by Fabien Potencier
Warning: Symfony 2.1 is no longer supported. Consider upgrading your applications to the most recent Symfony version.
Today, the Doctrine team announced the release of Doctrine 2.3.0. Congrats to them!
That's a good opportunity to release another Symfony 2.1 minor version. Symfony 2.1.2 comes with Doctrine 2.3.0 final and fixes a couple of minor bugs too (nothing to be excited about though).
Symfony 2.1.2 is also yet another release that tries to stabilize our usage of
Composer. Jordi fixed a small/annoying/major flaw in the way the
composer.lock
file worked, and hopefully, we now have a solid foundation to
manage our dependencies and to create a new Symfony project.
But first, you must upgrade Composer to its latest version; that's easy enough to achieve:
1
$ composer.phar self-update
Then, if you want to create a new Symfony project, download an archive or run the following command:
1
$ composer.phar create-project symfony/framework-standard-edition path/ 2.1.2
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 are closed.
To ensure that comments stay relevant, they are closed for old posts.
I run composer.phar install in the Symfony directory and get:
'Your lock file is out of sync with your composer.json, run "composer.phar update" to update dependencies'
This doesn't make me feel good. Additionally, when I add a new bundle to composer.json, I have run composer.phar update to get the new bundles rather than composer.phar install. Doing the update updates all of the packages to developmental packages (for example, Symfony goes to 2.1.3-DEV).
What am I doing wrong?
In the previous post symfony.com/blog/symfony-2-1-1-released someone mentioned a problem with overwriting the lock file.
Maybe we need a way to merge two composer.lock files?
Most imported thing would be check to compatibility between packages.
composer.phar update some/dependency
not to get the DEV versions.
Manully update your composer.json file with your own dependencies.
Now try this command :
composer.phar update nothing
Composer will compare the json file AND your lock file to update and get your missing files.
After this operation your composer.lock file will be updated with your dependencies (not the symfony's) and then you can use it for deploy your application.
Tell me back if it's ok for you.
The only problem is the good support of mongo in Mac OSX, cause BC when I want upgrade PHP to 5.4 (in my view, the php mongo driver is unstable).
Congrats !
MacBook-Pro:Repos greg$ composer.phar create-project symfony/framework-standard-edition symfony/ 2.1.2
Installing symfony/framework-standard-edition (v2.1.2)
- Installing symfony/framework-standard-edition (v2.1.2)
Downloading: 100%
Created project in symfony/
[ErrorException]
Undefined index: package
"To update to the new version, use update command. This will fetch the latest matching versions (according to your composer.json file) and also update the lock file with the new version."
So maybe we have a concept error (maybe not)
Instead of having on the composer.lock (cool for testing latest dev):
"symfony/symfony": "2.1.*",
"doctrine/orm": ">=2.2.3,
Then remove vendor folder, and run 'composer install' again.
"require-dev": {
"twig/twig": ">=1.6.0,
My commandline shows a number of updates such as:
- Updating symfony/symfony 2.1.x-dev (f23fd0 => 727331)
Checking out 7273311e1fb663ae7f5501f57a52ba9bd4db2ec3
Have i installed version 2.1.2 now? How can i verify this?
When running composer.phar install form the latest composer.lock file :
- Updating doctrine/common 2.3.x-dev (605b1b => bb0aeb)
[exec]
[exec]
[exec]
[exec] [RuntimeException]
[exec] Source directory /data/jenkins/workspace/zzzzz/vendor/doctrine/common has uncommitted changes.
[exec]
[exec]
[exec]
[exec] Exception trace:
[exec] () at phar:///data/jenkins/workspace/zzzzz/composer.phar/src/Composer/Downloader/VcsDownloader.php:135
[exec] Composer\Downloader\VcsDownloader->enforceCleanDirectory() at phar:///data/jenkins/workspace/zzzzz/composer.phar/src/Composer/Downloader/VcsDownloader.php:89
We cleaned completely the vendor dir before running the install
Any idea ?
Remove vendor directory, lock file.. and try again
Or, the BEST solution, create a new directory, run the command line to install Symfony from composer, wait 5 minutes, add your depencies in composer.json, and copy/paste your bundle/configuration !
Since SF2 is very well "fragmented" it's amazingly easy to import your bundles/config in a fresh install, good job @Symfony !
php composer.phar update is updating vendors to development version.
After some research, I found out that we can ask composer to update to stable versions only. Here is how I did it
1) Open composer.json file
2) Near the bottom you will find "minimum-stability": "dev"
3) Change it to "minimum-stability": "stable"
Now run php composer.phar install. It will only install Stable software versions.
I hope this helps someone.
Call to undefined method Symfony\Bundle\FrameworkBundle\Templating\Helper\SessionHelper::getFlashBag()
I admire and appreciate the hardwork, but please get the simple things right first.