Updating composer
Fixed documentation links for JMS bundles

The existing link leads to a server error. I've added a link to the JMSDiExtraBundle. Versions are as specified by 'composer.lock' file. In my opinion, every bundle listed here should have a link to some documentation.
Added description to composer.json
merged branch snc/composer-description (PR #323)

Commits
-------

1f0db79 Added description to composer.json

Discussion
----------

Added description to composer.json

This PR "fixes" the composer.json validation.

Before:
`$ php composer.phar validate
./composer.json is valid for simple usage with composer but has
strict errors that make it unable to be published as a package:
description : is missing and it is required`

After:
`$ php composer.phar validate
./composer.json is valid`
Check for PCRE > 8.0
merged branch vicb/check/pcre (PR #324)

Commits
-------

c7c44db Check for PCRE > 8.0

Discussion
----------

Check for PCRE > 8.0

related to symfony/symfony#4093
merged branch xuni/patch-1 (PR #322)

Commits
-------

ff596df Fixed documentation links for JMS bundles

Discussion
----------

Fixed documentation links for JMS bundles

The existing link leads to a server error. I've added a link to the JMSDiExtraBundle. Versions are as specified by 'composer.lock' file. In my opinion, every bundle listed here should have a link to some documentation.
raise required PHP version to 5.3.3
merged branch Tobion/php-version (PR #327)

Commits
-------

e5f337f raise required PHP version to 5.3.3

Discussion
----------

raise required PHP version to 5.3.3

closes symfony/symfony#2985
fixes symfony/symfony#4176
raised the minimum version of PHP to 5.3.3
Allowed renaming of "app" directory without breaking requirements checking
updated vendors (closes #329)
merged branch jalliot/composer-upstream (PR #314)

Commits
-------

e3fea40 Updating composer

Discussion
----------

Updating composer

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

by fabpot at 2012-04-20T04:53:55Z

For some reasons, composer does not work after this PR (assert(): Assertion failed).

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

by jalliot at 2012-04-20T07:34:38Z

I had the same problems some times and fixed it by removing the `*` constraint and putting `doctrine/orm: 2.2.2` instead for instance but that's not a good option...
@Seldaek Do you know why such a problem?

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

by Seldaek at 2012-04-20T07:40:10Z

Well, I do know we have one (or more?) assert issue still - hopefully @naderman can check it out this weekend. Until this is fixed I would advise keeping the strict requires as before, it puts less stress on the solver.
updated vendors
merged branch jmfontaine/requirements-checking (PR #328)

Commits
-------

9d1e6de Allowed renaming of "app" directory without breaking requirements checking

Discussion
----------

Allow renaming of "app" directory without breaking requirements checking

Sometimes one need to have an application directory which name should not be "app". For example, there is already an "app" directory and an "api" or an "admin" directory is needed to store a wholly different, yet related,  application.

Requirements checking has "app/cache" and "app/logs" hard coded so it fails if the application directory is not "app".

I changed this to be dynamically retrieved so any application directory name will work now on.