Closed soullivaneuh closed 8 years ago
Yeah, in the beginning I thought BC break shouldn't be too problematic for a Composer plugin but indeed, I need to avoid BC breaks like for classical projects.
Sorry for the inconvenience!
Now you know why! ;-)
Finally found a way to fix this kind of issues.
Starting from the next release (see #22), all the classes will be autoloaded when the plugin is enabled. Not the cleanest solution but should just work because I don't want the plugin to fail even if the user update to an eventual 2.0 breaking BC.
Thanks again for your issue ;)
This is thrown just after upgrading to
v1.1.0
:If I run the command again, no problem.
I suspect BC breaking code. This should be handled smoothly even for a composer plugin to avoid this kind of weird error.