Closed stgeneral closed 9 years ago
I have just encountered this as well. I tthink it fails because it tries to use a class from the component installer after robloach/component-installer
is already removed. By requiring the component installer in the root composer.json
this can only partially be fixed because it will still occur when removing the component installer itself.
If there is no simple solution to detecting if the component installer shall remove itself then I suggest autoloading all classes at the beginning so the autoloader will never be called to load a class from a file that is no longer there.
I have the same problem
Wouldn't it be enough to use class_exists
before trying to instantiate the class?
I have the same problem. But it appeared once, the next time for update it was no longer
Still occurs, we use CloudControl to deploy our code to their instances. Their deployment process supports using Composer, but removing the component installer results in failed deployments..
Removal succeeds with this PR:
composer update --verbose -vv
Loading composer repositories with package information
Updating dependencies (including require-dev)
- Removing robloach/component-installer (dev-master)
- Removing kriswallsmith/assetic (v1.2.1)
- Removing symfony/process (v2.6.6)
Writing lock file
Generating autoload files
Compiling component files
Process class 'ComponentInstaller\Process\CopyProcess' not found, skip this process
Process class 'ComponentInstaller\Process\RequireJsProcess' not found, skip this process
Process class 'ComponentInstaller\Process\RequireCssProcess' not found, skip this process
Process class 'ComponentInstaller\Process\BuildJsProcess' not found, skip this process
Thanks a lot, guys!