This makes Cilex more inline with Silex 2.0 and uses pimple 3. there is an issue with silex/api as have not yet been updated with the pimple 3.0 requirement.

I removed a bunch of providers as they can now be used from silex/providers. Also i moved the ConsoleServiceProvider into Cilex directly, mostly because its a hard requirement. If we want a seperate package for it, we can use a subsplit on src/Cilex/Provider as the silex/providers package does.

so one of my visions was that Cilex and Silex could share extensions. right now @mvriel introduced a new ServiceProviderInterface interface inside the Cilex namespace. i talked briefly with him on IRC today where @mvriel said he wants to switch the Silex one, which obviously would imply a dependency on Silex, which imho is fine, but i don't know how specifically he wants it to play out given the Application type hint.

but it does raise the question of if we are not making things needlessly complex by not doing this all inside Silex. then again doing it all inside Silex would go against the entire "micro" idea. so maybe we do need to ask the Silex guys to make things a bit easier for us ..

/cc @igorw @jmikola

Cilex is currently bound to pimple ~1.0. When included in a complex composer.json dependency tree, cilex bounds pimple to the older version. This is causing problems with a variety of other packages, such as elasticsearch.

Want to use Pimple 2.* in my application but composer seeing conflict with Cilex and doesn't let me. This is also providing the use of PhpDocumentor since it uses Cilex as well. Have NOT looked to see what all changes were make on Pimple but always prefer using most up to date versions when possible. After a quick look it looks like the main change is that instances are shared by default like share() would do and you use factory() to get something like the old behavior if my reading of the code is right. Not sure how this effects Cilex.

When I try to compile:

cilex/bin$ php ./compile

PHP Fatal error: Uncaught exception 'RuntimeException' with message 'The git binary cannot be found.' in /media/disk2/darek/yii/cilex/src/Cilex/Compiler.php:43 Stack trace: #0 /media/disk2/darek/yii/cilex/bin/compile(13): Cilex\Compiler->compile() #1 {main}

thrown in /media/disk2/darek/yii/cilex/src/Cilex/Compiler.php on line 43

Fatal error: Uncaught exception 'RuntimeException' with message 'The git binary cannot be found.' in /media/disk2/darek/yii/cilex/src/Cilex/Compiler.php on line 43

RuntimeException: The git binary cannot be found. in /media/disk2/darek/yii/cilex/src/Cilex/Compiler.php on line 43

but git is of course available on system

cilex/bin$ whereis git git: /usr/bin/git /usr/bin/X11/git /usr/share/man/man1/git.1.gz

cilex/bin$ git usage: git [--version] [--exec-path[=]] [--html-path] [--man-path] [--info-path] [-p|--paginate|--no-pager] [--no-replace-objects] [--bare] [--git-dir=] [--work-tree=] [--namespace=] [-c name=value] [--help] []

PHP Fatal error: Uncaught exception 'InvalidArgumentException' with message 'The "/src/Cilex/../../vendor/symfony/class-loader/Symfony/Component/ClassLoader" directory does not exist.' in /vendor/symfony/finder/Symfony/Component/Finder/Finder.php:497

• Added a demo run.php file in bin/
• Added .idea to gitignore
• Added a demo box.json
• Improved the readme file to explain how to create and use new commands, as well as creating a phar file using box

This fixed #27

I know this is a BC but since it targets 2.0 i think it is okay.

The reason for renaming command to add is that it adds the command to the application, which is the same terminology used by a normal Console Application. Also when using closures the name command feels more natural.

here is an example, the syntax should be equal to the one used in Silex with its get, post etc functions.

<?php

$cilex = new Cilex\Application;
$cilex->command('my-command-name', function ($input, $output) {
    // do something
});

$command = $cilex->command('my-command-name', function ($input, $output) {
    // do something
});

$command->addOption(); // etc.

Fresh install: 1008 git clone https://github.com/Cilex/Cilex.git 1009 cd Cilex 1010 composer update 1011 composer install 1012 php bin/compile 1013 php cilex.phar PHP Warning: require(phar:///private/tmp/Cilex/cilex.phar/vendor/composer/include_paths.php): failed to open stream: phar error: "vendor/composer/include_paths.php" is not a file in phar "/private/tmp/Cilex/cilex.phar" in phar:///private/tmp/Cilex/cilex.phar/vendor/composer/autoload_real.php on line 29

Warning: require(phar:///private/tmp/Cilex/cilex.phar/vendor/composer/include_paths.php): failed to open stream: phar error: "vendor/composer/include_paths.php" is not a file in phar "/private/tmp/Cilex/cilex.phar" in phar:///private/tmp/Cilex/cilex.phar/vendor/composer/autoload_real.php on line 29 PHP Fatal error: require(): Failed opening required 'phar:///private/tmp/Cilex/cilex.phar/vendor/composer/include_paths.php' (include_path='.:') in phar:///private/tmp/Cilex/cilex.phar/vendor/composer/autoload_real.php on line 29

Fatal error: require(): Failed opening required 'phar:///private/tmp/Cilex/cilex.phar/vendor/composer/include_paths.php' (include_path='.:') in phar:///private/tmp/Cilex/cilex.phar/vendor/composer/autoload_real.php on line 29

The register function of Cilex\Application supposedly allows you to register a Silex ServiceProvider (\vendor\cilex\cilex\src\Cilex\Application.php:97-99), but when actually trying to register the Silex ServiceProvider, you hit:

Catchable fatal error: Argument 1 passed to Igorw\Silex\ConfigServiceProvider::register() must be an instance of Silex\Application, instance of Cilex\Application given

If it is to be compatible with Silex service providers, the Interface definition typehint must be dropped or if it is not compatible, lines \vendor\cilex\cilex\src\Cilex\Application.php:97-103 should be removed.

This seems related to https://github.com/Cilex/Cilex/issues/3.

Added the console-service-provider library to the finder that compiles the phar, fixes this exception I was always getting: PHP Fatal error: Class 'Cilex\Provider\Console\ConsoleServiceProvider' not found in phar://

Greetings from the #SymfonyConHackday2017. This PR fixes a small compatibility problem with Symfony 4 and updates the composer.json file to allow the installation of Symfony 4 components.