-
-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Box does not work with Composer 2.2 (allowed-plugins) #580
Comments
I've reproduced this problem in a minimal repo: https://github.com/ondrejmirtes/composer-issue/actions/runs/1765720462 I can offer some funds towards fixing this problem, so don't hesitate to reach out. Thanks. |
Should be fixed with 3.15! |
I still reproduce it in Infection repository with 3.16.0 both with
|
I agree. This isn't related to allow-plugins. It still doesn't work with latest Box and Composer. |
Ok finally found the issue. The problem is that The way Box works is:
This means that if you have a dev plugin, e.g. I think this could be solved in Composer, but I also cannot just wait for a fix there so I'll likely need to temper the content of |
What if you add |
@jaapio in which case this would break the bundling of any Symfony app which uses Flex. I'm not familiar enough with other frameworks, but this makes me believe there could be other affected too so it's not really the solution. |
Have just run into this here as well. I've worked around it by:
Composer's behaviour here isn't unreasonable, though. I wouldn't expect a package manager to remain operational if critical files were deleted, and from the discussion here and a quick read of the documentation, it seems reasonable for Would it be feasible to use |
Yes and no. Currently the whole process is:
What the above entails would mean:
So it's really not a trival amount of changes and probably a big performance hit too. |
@theofidry While working on final version of BOX Manifest v4.0, I've encounter this problem too when I tried to use the I recommend to add a note on documentation like it was done for At least for me it worked ! BTW, I've also noticed that the BOX output did not display that we have effectivly changed directory. It may be cool to have such info. For example with vendor/bin/box compile -c box.json.dist -vvv -d tests/fixtures/phario-manifest-2.0.x-dev/ Prints following output
Note Line |
…toload setting : see issue box-project/box#580)
Bug report
Box fails compiling a prefixed PHAR with the brand new Composer 2.2 is used:
Note: Infection had issues with Composer 2.2 too, fixed by adding
allowed-plugins
configuration: infection/infection#1624The text was updated successfully, but these errors were encountered: