bower install requires manual intervention (breaks travis CI build)

[sogko]

"bower install" unable to determine angular version and requires manual intervention to choose the right version.

See:
https://travis-ci.org/linnovate/mean/builds/17452159

Unable to find a suitable version for angular, please choose one:
    1) angular#1.2.8 which resolved to 1.2.8 and has mean as dependants
    2) angular#1.2.9 which resolved to 1.2.9 and has angular-cookies#1.2.9, angular-mocks#1.2.9, angular-resource#1.2.9, angular-route#1.2.9 as dependants
    3) angular#>= 1.0.2 which resolved to 1.2.10-build.2176+sha.e020916 and has angular-ui-utils#0.1.0 as dependants
    4) angular#>=1 which resolved to 1.2.10-build.2176+sha.e020916 and has angular-bootstrap#0.10.0 as dependants
Prefix the choice with ! to persist it to bower.json
[?] Answer: 

[sogko]

issue fixed in #242 , pending request merge

[tobalsan]

by the way, this step is missing in the main README (confused me fo a moment)

[fyockm]

From what I've just seen, the fix in #242 was just a stop gap till the next version of angular was released, and as a matter of fact it already has been (now on 1.2.11). Now that we're current with angular, I think the best approach is to mark it as latest in bower.json, which I've done in #236.

@tobalsan bower install should not be necessary as a separate step. It should happen automatically as a postinstall script, as can be seen in package.json. However, if npm install fails, I've seen this not work. We might consider adding a note about it in README.md.

[liorkesos]

#236 was merged and we adopted Drew's suggestion. This isn't supposed to happen again.