psalm/assets/psalm-phar/composer.json

{
	"name": "psalm/phar",
	"description": "Composer-based Psalm Phar",
	"license": ["MIT"],
	"require": {
		"php": "^7.1"
	},
	"conflict": {
		"vimeo/psalm" : "*"
	},
	"bin": ["psalm.phar", "psalm", "psalter", "psalm-language-server", "psalm-plugin"]
}
Add executable PHP files to PHAR distribution Previously a user of the phar distribution would have to invoke psalm as `vendor/bin/psalm.phar`. This is different to the command given in the psalm documentation, `vendor/bin/psalm` I also copied all files from the psalm/phar repo into assets/psalm-phar, so that development can be concentrated in this repo. The travis-deploy-phar.sh should copy any changes made back into the psalm/phar.git repo. 2019-06-07 00:12:53 +02:00			`{`
			`"name": "psalm/phar",`
			`"description": "Composer-based Psalm Phar",`
			`"license": ["MIT"],`
			`"require": {`
Update PHP version req in phar to match non-phar requirement I'm guessing there's no difference between the two which means one needs 7.1 and the other only needs 7.0 Co-Authored-By: Bruce Weirdan <weirdan@gmail.com> 2019-06-07 11:05:31 +02:00			`"php": "^7.1"`
Add executable PHP files to PHAR distribution Previously a user of the phar distribution would have to invoke psalm as `vendor/bin/psalm.phar`. This is different to the command given in the psalm documentation, `vendor/bin/psalm` I also copied all files from the psalm/phar repo into assets/psalm-phar, so that development can be concentrated in this repo. The travis-deploy-phar.sh should copy any changes made back into the psalm/phar.git repo. 2019-06-07 00:12:53 +02:00			`},`
Don't allow installation of psalm/phar and vimeo/psalm in the same project The scoped and non-scoped code don't work together. 2019-06-07 22:49:41 +02:00			`"conflict": {`
			`"vimeo/psalm" : "*"`
			`},`
Add executable PHP files to PHAR distribution Previously a user of the phar distribution would have to invoke psalm as `vendor/bin/psalm.phar`. This is different to the command given in the psalm documentation, `vendor/bin/psalm` I also copied all files from the psalm/phar repo into assets/psalm-phar, so that development can be concentrated in this repo. The travis-deploy-phar.sh should copy any changes made back into the psalm/phar.git repo. 2019-06-07 00:12:53 +02:00			`"bin": ["psalm.phar", "psalm", "psalter", "psalm-language-server", "psalm-plugin"]`
			`}`