test minimal version

[dbu]

No description provided.

[dbu]

need to wait on doctrine/phpcr-odm#634

[dbu]

the remaining issue is deprecation warnings because i also added symfony 2.7 . will have a look at them.

[dbu]

@wouterj is there a way we can get rid of these deprecation warnings? but i don't really see how we can change the code and not break symfony 2.3 support. or is it the code coverage that somehow makes the build a failure?

[wouterj]

@dbu if you remove 2.7 tests from this PR, I'll create another one with the deprecation fixes. These deprecation notices can be fixed without breaking 2.3 support.

[dbu]

great. removed 2.7 from this PR

[wouterj]

this line should be composer self-update || true. As 5.3.3 doesn't have SSL on Travis, Composer can't run self-update.

[dbu]

@wouterj hm so composer self-update actually works, but fetching packages.json in composer update does not work: https://travis-ci.org/doctrine/DoctrinePHPCRBundle/jobs/61107070

[wouterj]

@dbu seems like composer usage is now completely broken on PHP 5.3.3 builds

[wouterj]

@dbu it seems like composer usage is now complete broken on Travis for 5.3.3 (I saw that the tests were broken for Symfony too)

[dbu]

crap. should we just say php 5.3 and hope on good luck for people still on 5.3.3?

[wouterj]

@dbu the tests on 5.3.3 should be fixed now. see http://seld.be/notes/composer-hosting-improvements :

While the whole change happened without packagist downtime, there were a few minor issues early last week with the composer homepage. Today I had to re-enable http (i.e. no-TLS) access to packagist.org as people are still relying on accessing it without the openssl extension. This is not great but the travis 5.3.3 builds are missing openssl so it's not realistic to require it, hopefully in a year or two when 5.3 is a thing of the past we can go full-TLS.