Closed jackcsk closed 8 years ago
Sorry for the hurdles, as I found that the last pull request was from a branch I used to test the travis-ci change
I've found a better way where this is all handled in travis instead of messing with the composer.lock file which will cause issues long term.
Ok, sorry for the mess around I've fixed the test builds on travis so the project is not dependant on composer.lock anymore. If you could update this PR with the composer from develop then I can merge this in. You aren't required to do any fancy composer update
hacks to get this to work anymore.
Thx. I've merged the updates, but it seems like travis-ci doesn't install phpunit properly?
I think I know what the problem is. If you do a composer update and commit the lock file it should work. Without the lock file updated to include phpunit the 2 that failed will always fail. Those failed tests are testing the installed composer.lock file. The other tests run composer update in one form or another which means the package gets installed on those. Anyway update and it should all start working.
I've deleted the composer.lock, and it will be re-generated on next "composer install". That fixes the travis-ci issue.
Please add the lock file back based on the lock file in the develop branch will be fine and this will work for your PR to. I can't accept this PR without the lock file or the lock file you previously generated with the php 5.3 dependancy that you then removed.
@mofodojodino: I've added the composer.lock file as you requested. I have to run composer update
to update the composer.lock for the phpunit to install.
Thanks @jackcsk
Hey @jackcsk, just letting you know I've released your contribution as v1.3.0. Thanks for you contribution.
https://github.com/mofodojodino/ProfanityFilter/releases/tag/1.3.0