Updated dependency version constraints

[stevenroose]

I was not able to get the tests running, but I'll take a look at the result from Travis to see if this causes issues.

[mhevery]

Thanks for your contribution! In order for us to be able to accept it, we ask you to sign our CLA (contributor's license agreement). CLA is important for us to be able to avoid legal troubles down the road.

For individuals (a simple click-through form): http://code.google.com/legal/individual-cla-v1.0.html

[stevenroose]

I filled in the CLA. Sadly, Travis seems to fail for this change. I cannot get the tests working, so I can't test which of the dependencies I upgraded is the one that causes the problem.

Can anyone who has the project testing environment setup please upgrade the dependencies one by one and push the ones that cause no problem?

Currently, it is not possible to have a project that uses both polymer and angular, which is kind of sad IMO.

[stevenroose]

I'm trying to upgrade every dependency one by one and wait for Travis to see which one is the problem. Hopefully I can upgrade most of them. Will notify when its done.

But still, if someone with the testing environment setup could try this, it would be much more efficient...

[youssefgh]

Its seems that the priority now for Angular team is V2
I hope that V1.1 got released soon and that deps got upgraded there

[rkirov]

It was easier for us to upgrade all the deps in one PR, so we just landed #1632. Thus I am closing this PR, but nevertheless thanks for creating it and trying to work through the Travis' failures.

@youssefgh v1.1 will be released in a few weeks.