claroline/CoreBundle — pull request #218 by maxailloud (2013-11-29 14:28:36+00:00)
Title: Bundle that doesn't need configuration file, or bundle that is configured by an other bundle should be activated

I'm in the case where I let my bundle deal with its own dependency, with its composer file, and I don't want to add my dependncies in the list of bundle with empty config in the [ClarolineCoreBundle.php](https://github.com/claroline/CoreBundle/blob/master/ClarolineCoreBundle.php#L44) file to make them active.

For my bundle if I don't update the core I can't use it, it's a non-sense.

So if a bundle is not defined in the config list bundle we just return a default config object and we guess that this bundle may not need configuration or is configured in an other place.

What do you think?
Can it be a side-effect to this modification?