composer.json depends on all jackalope versions

[dbu]

i think we should not depend on all jackalope versions, but just on phpcr-implementation.

then have the code for the different variants ready. when building the standalone phar, it makes sense to embed all supported implementations, but this is a phar / setup task.

when the shell is embedded in other projects, it should not bring all those dependencies. maybe we should split out a phpcr-shell-standalone or phcpr-shell-cli for standalone use and packaging?

[dantleech]

agreed. i guess we just need a build script or similar to create the PHAR and ensure that the required deps are in place.

[dantleech]

I think we should create a metapackage, maybe phpcr-shell-full.

[cordoval]

try to have the usable package be the phpcr-shell name though as it would be very confusing

[dantleech]

I think simply moving the requirements to require-dev is enough, as the PHAR is always built from a dev environment: #97

[dbu]

you could also have a build script to do one phar per jackalope flavor. the script would composer require each of the supported implementations, then build the phar, then remove it and require the next.

[dantleech]

Yeah, that could be something to think about in the future, although I think for now bundling all the implementations in one PHAR works. I also thought about having a "plugin" system where you could install things locally in ~/.phpcrsh/plugin for example.

[dantleech]

Fixed by #97