Nicolas Grekas

> Then there sure is no need to load any other tags of symfony/messenger than the ones matching 4.3.*. If we do this, then composer will not be able to...

> I guess if we filter out everything that does not match our root requirements, the whole abandoned stuff would not be needed in the first place That would break...

@naderman I totally agree: as I suggested in the description, this PR is a step towards this target. I feel safer to take this path than to dream about an...

@mabar yes, phpstan would read `tools/test/vendor/` to learn everything it needs to know about phpunit. About phars, this has been discussed in the linked issue #9636: they don't work well...

@gmsantos this works already, what else would you need? ``` "scripts": { "test": [ "./tools/test/phpunit" ] }, ```

@glensc @gmsantos now achieved by changing the `bin-dir` in the composer.json file, see updated description.

@Jean85 there is one autoloader per "tools" directory, which can load the app or not depending on the `app/app` in the require above. When multiple tools should share the same...

I suppose you mean transitive dependencies, right? What I wrote in the description: the `vendor/` dir of the app will be used as the package repository for shared deps. This...

I think you've got this right. Which issue are you talking about? To me they are all solved: - if a tool needs to be able to autoload the classes...

Please have a look at #9792