Document that container aware migrations are not special anymore

[goetas]

closes #349
closes #350

[SenseException]

This information might be relevant for the documentation too. I don't know in which chapter it would fit in though.

[goetas]

@SenseException i could not find any reference to this feature in the documentation, I think that was something available but never documented, so i've added a section to document that feature now.

[fabpot]

Is there anywhere I can read about the decision to remove support for injecting the Container?

[goetas]

@fabpot

Is there anywhere I can read about the decision to remove support for injecting the Container?

Not really. it has been done as part of the major refactoring done in v3. The rationale behind them is to remove the magic (some command injecting dependencies based on marker interfaces) and let people use dependency injection do the job by providing dependencies they might need.

[goetas]

I have in plan to work on this and to provide a factory (enabled by default when using the bundle)that will provide the container if the migration is "container aware"

[goetas]

#368 will introduce a default migration factory that will check if the migration class implements the ContainerAwareInterface class.