[FrameworkBundle] recursively resolve container parameter placeholders
for arrays in router _defaults
Update src/Symfony/Component/Validator/Resources/translations/validators.ro.xlf

Pluralization of $minMessage, $maxMessage and $exactMessage is required in LengthValidator.
The English version is already updated.
merged branch raresvla/master (PR #5646)

This PR was submitted for the master branch but it was merged into the 2.1 branch instead (closes #5646).

Commits
-------

4509c9e Update src/Symfony/Component/Validator/Resources/translations/validators.ro.xlf

Discussion
----------

[validator] Fixed error messages for Length validator, locale: "ro"

....ro.xlf

Pluralization of $minMessage, $maxMessage and $exactMessage is required in LengthValidator.
The English version is already updated.
[Form] Fixed negative index access in PropertyPathBuilder
merged branch bschussek/issue5605 (PR #5653)

This PR was merged into the 2.1 branch.

Commits
-------

2d41229 [Form] Fixed negative index access in PropertyPathBuilder

Discussion
----------

[Form] Fixed negative index access in PropertyPathBuilder

Bug fix: yes
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: #5605
Todo: -
License of the code: MIT
Documentation PR: -
[HttpFoundation] Fixed #5611 - Request::splitHttpAcceptHeader incorrect result order.

* Makes items with equal q-values return in the original provided order.
* Fixes tests to reflect this behavior
[Form] Hardened code of ViolationMapper against errors
merged branch bschussek/issue5578 (PR #5655)

This PR was merged into the 2.1 branch.

Commits
-------

2568432 [Form] Hardened code of ViolationMapper against errors

Discussion
----------

[Form] Hardened code of ViolationMapper against errors

Bug fix: no
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: -
Todo: -
License of the code: MIT
Documentation PR: -

This ticket improves the code of ViolationMapper to reduce the risk of bugs and in order to make further bug fixing easier. It was implemented while trying to solve #5578 and is semantically equivalent to the previous version.
validateOptionValues throw a notice if an allowed value is set and the corresponding option isn't.
Unit test for patched method OptionsResolver::validateOptionValues().
merged branch fabpot/moved_optionsresolver_1 (PR #5657)

This PR was submitted for the master branch but it was merged into the 2.1 branch instead (closes #5657).

Commits
-------

939d387 Unit test for patched method OptionsResolver::validateOptionValues().
61d0f80 validateOptionValues throw a notice if an allowed value is set and the corresponding option isn't.

Discussion
----------

Patch method OptionsResover::validateOptionValues().

This PR was submitted on the symfony/OptionsResolver read-only repository and moved automatically to the main Symfony repository (closes symfony/OptionsResolver#1).

When we define allowed values for an optional option and the corresponding option was not set. On resolve, OptionsResover::validateOptionValues() was throwing a notice.
[Translation] forced the catalogue to be regenerated when a resource is added (closes symfony/Translation#1)
[TwigBundle] added support for Twig namespaced paths (Twig 1.10)

In a template, you can now use native Twig template names, instead of
the Symfony ones:

Before (still works):

    {% extends "AcmeDemoBundle::layout.html.twig" %}
    {% include "AcmeDemoBundle:Foo:bar.html.twig" %}

After:

    {% extends "@AcmeDemo/layout.html.twig" %}
    {% include "@AcmeDemo/Foo/bar.html.twig" %}

Using native template names is also faster.

The only drawback is that the new notation looks similar to the way we
locate resources in Symfony, which would be
@AcmeDemoBundle/Resources/views/Foo/bar.html.twig. We could have used
the same notation, but it is rather verbose (and by the way, using this
notation did not work anyway in templates).
merged branch kerihenare/ticket_5611 (PR #5612)

This PR was merged into the 2.0 branch.

Commits
-------

6c59fbd [HttpFoundation] Fixed #5611 - Request::splitHttpAcceptHeader incorrect result order.

Discussion
----------

[HttpFoundation] Request::splitHttpAcceptHeader incorrect result order.

Bug fix: yes
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: 5611

Makes items with equal q-values return in the original provided order. Fixes tests to reflect this behavior.

---------------------------------------------------------------------------

by kerihenare at 2012-10-02T20:59:11Z

To avoid confusion over the modified language test I have instead created new tests.
[DomCrawler] Allows using multiselect through Form::setValues().
merged branch pawaclawczyk/bugfix-multiselect-setvalues (PR #5502)

This PR was squashed before being merged into the 2.1 branch (closes #5502).

Commits
-------

6200290 PSR-2 correct.
5c17388 Allows using multiselect through Form::setValues().

Discussion
----------

[DomCrawler] Allows using multiselect through Form::setValues().

Patch allows set multiple values in select using setValues() method, as it is used in Symfony\Component\BrowserKit\Client::submit().
[2.2][Console] Test default input defintion and default helper set
merged branch dirkaholic/testDefaultInputDefintion (PR #5668)

This PR was squashed before being merged into the master branch (closes #5668).

Commits
-------

1117499 [2.2][Console] Test default input defintion and default helper set

Discussion
----------

[2.2][Console] Test default input defintion and default helper set

Bug fix: no
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: -
Todo: -
License of the code: MIT
Documentation PR: -

See: https://github.com/symfony/symfony/pull/5638
fixed CS
Updated lithuanian validation translation