« Previous | Next » 

Revision 2d583053

ID2d5830538c67abb39c316081abe4bc2f21e77c6d
Parent 86f9b499
Child f5872fa3

Added by Christian Müller almost 7 years ago

[!!!][TASK] Exclude Non-Flow packages from object management by default

With this change all packages, that are not of one of the "typo3-flow-*"
composer types, are excluded from object management by default.

Previously the had to be excluded explicitly with the
``TYPO3.Flow.object.includeClasses`` setting.

To activate object management for Non-Flow packages, the newly introduced
setting ``TYPO3.Flow.object.includeClasses`` can be used. It works in
the same way as ``excludeClasses``, apart from not allowing wildcards for
the package.

This is a breaking change in case proxy building for non-flow packages
was expected. In these cases packages have to be included explicitly now::

TYPO3:
Flow:
object:
includeClasses:
'non.flow.package' : ['.*']

To exclude classes from Flow packages a non-matching or empty expression
can be specified::

TYPO3:
Flow:
object:
includeClasses:
'Some.Flow.Package' : []

The ``excludeClasses`` setting is deprecated but still evaluated.

Change-Id: Iaf699889138d13cae8fbc1179fa0bcb02ac6e16d
Releases: master
Resolves: FLOW-103

  • added
  • modified
  • copied
  • renamed
  • deleted