> this requires that any custom class is autoload-able or load it somehow else (auto-prepend .. though that is ugly).

True, @patrickallaert some way to specify a required file maybe?

> it would be more inline with the philosophy of Symfony2 to have such a class in the app (ie. ezpublish) dir.

Yes, this is one of the topic further up in the PR comments, our problem is that the Symfony approach causes issues for updates and upgrades (conflicts / wiped customizations / ..), so the idea behind this approach is to allow people to extend these files withouth changing them.

But now that you mention it this should probably be tackled upstream instead/as-well, otherwise the approach is vastly different when you want to install eZ Publish 5 kernel inside a symfony-standard distribution as opposed to getting symfony as part of eZ Publish5-distribution which is the case in this repo.

@patrickallaert, @lsmith77, @lolautruche Something to discuss at the ezunconf in Montpellier maybe? (find a approach that could be contributed and accepted in symfony-standard)