Drush does not use .php extension after 9.x

[taz77]

After Drush 9.x the ./composer/vendor/bin/drush.php was dropped. 8.x versions of Drush had both the drush.php and the drush versions. Since Drupal_TI requires at least 8.0.* there should be no backward compatibility problem.

[coveralls]

Coverage remained the same at 100.0% when pulling 95e39a1 on Fastglass-LLC:fix-path-to-drush into 5316cdd on LionsAd:master.

[taz77]

Updated PR with changes in Master.

[WengerK]

Thanks for this PR, I applied it on my own PR some days ago (as I get the same issue as you #126).

I would like to finish #126 before merging any more changes. For now we can't trust our tests CI as a lot of them are deprecated code or no up-to-date - wanna help me on #126 ?

[taz77]

How about we get this merged? The issue addressed here is preventing Drupal_TI from running at all. Being a module maintainer, I need my tests to run and I cannot move forward because it cannot find Drush.

[taz77]

@WengerK do you have rights to the Packagist account?

[WengerK]

Nope, what for ?

[taz77]

Packagist needs to be updated. It does not have the latest dev-master code.

[WengerK]

You can force the commit in your own travis.yml - if needed.

[LionsAd]

What do I need to do to refresh packagist?

[taz77]

@LionsAd When you sign into Packagist and go to your projects there is an "Update" button. This will cause Packagist to get the latest dev.

@WengerK Yes, you can specify a hash but that causes Composer to run git to pull from Github which if you don't have Github credentials setup then you typically will never be able to pull because Travis maxes out the API limits on Github at any given time for anonymous calls.

[LionsAd]

Done, thanks for bringing that to my attention.