I'm definitely in favor of this split... if we can do it without BC breaks... so the old class names must still exist.

By the way, I think it would make#8848 obsolete.

@fabpot The only class names that were changed so far are the tests, where the namespaces changed fromSymfony\Component\Security\Tests\{Core|Acl|Http} toSymfony\Component\Security\{Core|Acl|Http}\Tests. I don't think the tests are part of our public API though.

I'm not quite sure what to do about theResources directory. We could just leave it where it is, meaning you need to installsymfony/security if you want to use the resources. Moving them would be a BC break.

@fabpot There is no BC breaks. Only test classes are renamed in this PR. All other classes are still the same.

for the resources, I think we should find a way to have them in one of the components. Having to require thesymfony/security component to get them kind of defeats the possibility to avoid installing the ACL system.

@stof Well one possibility would be to move them to wherever they belong (Core or HTTP?), and to add a Composer post-install hook that copies them to the main directory insymfony/security.

I suppose that the goal is to move the classes themselves as well, right?

@bschussek a post-install hook is not a good BC layer as it has to be added by the user in the root composer.json

@fabpot The Security component is already divided in 3 distinct namespaces. This PR simply creates the subtree splits of these 3 folders.

... I need to sleep more ;)

For the Resources directory, I wouldcopy to Core (as Http depends on Core), deprecate the old location, and remove it in 3.0. In the meantime, we must ensure that both Resources directory are kept in sync.

Closing in favor of#9064