Document the new Class Map generator (Symfony 2.1)

[fabpot]

A cookbook explaining why and how you can use the new class map generator (refs symfony/symfony#3394).

[wouterj]

@weaverryan this should get a 'Actionable' and 'Missing Docs' label.

[wouterj]

Hmm, after looking at this I think this should be closed. Packages without proper autoloading should be configured using Composer. I don't see any value of the ClassMapGenerator in Symfony 2.3 and higher (since 2.2 and lower are not maintained anymore, we shouldn't worry about them).

What do you think @fabpot, @cordoval, @weaverryan ?

[weaverryan]

I agree - is there a use-case for this class at this point? If there is, that would make documenting it much easier anyways :).

[xabbuh]

@fabpot Do you have an actual use-case for the class map generator?

[wouterj]

@xabbuh assume you include a 3th party project which doesn't have autoloading. It doesn't follow the PEAR or PSR standards, so there is no way you can write an autoloader for it instead of hardcoding all paths for each classes. In such cases, you can simply use the class map generator, which will generate a class map of all classes of that project and their location, so you can use that map in your autoloader.

[xabbuh]

With #4081 being merged, this can be closed.