[TASK] Priority is not execution order in for Extractors 96/26696/2
authorSteffen Ritter <info@rs-websystems.de>
Wed, 8 Jan 2014 18:08:02 +0000 (19:08 +0100)
committerSteffen Ritter <info@rs-websystems.de>
Thu, 30 Jan 2014 16:38:13 +0000 (17:38 +0100)
commit036063910a352a3c3b62dc370f642f8b9ee2496f
treee840043cc815a2b6dff5f00cd2b5e519715305e8
parent4fbaa7ec82553ac2febac935c3ac3e5c78167747
[TASK] Priority is not execution order in for Extractors

When the meta-data extraction services have been introduced it
silently has been assumed that the defined priority can be
used as execution order. In fact the priority just defines which
data takes precedence of another. In fact you might have an
extraction service which has highest priority for the fields it
serves but on the opposite should run as first, so other
extraction services already can use the data.

This change adds a second "priority" for that purpose and adapts
the indexing process accordingly.

Resolves: #54228
Releases: 6.2
Change-Id: I649fc8b91103ab518e5a692bf73c54851e8b70b1
Reviewed-on: https://review.typo3.org/26696
Reviewed-by: Frans Saris
Reviewed-by: Wouter Wolters
Reviewed-by: Stefan Neufeind
Reviewed-by: Ingo Schmitt
Reviewed-by: Steffen Ritter
Tested-by: Steffen Ritter
typo3/sysext/core/Classes/Resource/Index/ExtractorInterface.php
typo3/sysext/core/Classes/Resource/Index/ExtractorRegistry.php
typo3/sysext/core/Classes/Resource/Index/Indexer.php