The field type definition registry has been moved out to compatibility artifact. The reason for that was that the current (m5) field definitions and related factories are too Vaadin 7 bound and we have had to implement the Vaadin 8 replacements from scratch for both.

Instead of trying to accommodate both flavours of definitions and factories into FieldTypeDefinitionRegistry, we have deprecated the latter, but yet haven't come up with a replacement solution.

There are several options for that, but probably we should not introduce yet another registry (field def <-> factory mapping doesn't seem to justify the need for a factory anyway).

Acceptance criteria:

• there is a non-deprecated convenient way to bind (and re-bind) reworked field definitions to the factories.
• there is still a way to override the stock magnolia bindings with the custom ones.

Note:
This impacts content types.

NOTE: The current way of binding field defs to factories in the new UI framework is stubbed in the following class:
info.magnolia.ui.framework.databinding.registry.ComponentTypeDefinitionRegistry