Project

General

Profile

Actions

Feature #67293

closed

Generalize the DependencyResolver to be useful for more purposes

Added by Markus Klein almost 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Backend API
Target version:
Start date:
2015-06-04
Due date:
% Done:

100%

Estimated time:
PHP Version:
Tags:
Complexity:
medium
Sprint Focus:

Description

The DependencyResolver is currently used for the PackageManager to determine the loading order of extensions.
The same mechanism is useful for other purposes, eg. hook ordering, as well.

Therefore the DependencyResolver should be extracted from the Package context.

Adjusting the DependencyResolver slightly, makes it a powerful tool to resolve dependency trees.

It will support:
  • building a dependency tree based on "before" and "after" information
  • transformation of the tree into a sorted list

The PackageManager needs only small adjustments on the way it uses the DependencyResolver.
Basically "dependencies" and "suggestions" of packages are matched to "after"; "before" is not supported for packages.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #52828: extTables cache file creation does not respect extension orderClosed2013-10-15

Actions
Actions

Also available in: Atom PDF