Feature #30258

Support optional package dependencies

Added by Christopher Hlubek over 9 years ago. Updated over 9 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-09-24
Due date:
% Done:

0%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

FLOW3 should support optional package dependencies to enable the usage of classes inside a package that belong to a suggested (optional) package. Right now the reflection service will die with a fatal error.

Possible solutions:

1. Blacklisting of class folders

The Package.php could blacklist folders inside Classes depending on available packages. This way , the class that relies on an optional package would not be reflected and loaded.

2. Fake empty class

The classloader could fake an empty class (with throw statements on access) just to satisfy the reflection of a class.


Related issues

Related to TYPO3.Flow - Bug #28213: Sites Configuration should overrule package ConfigurationResolved2011-07-14

Actions
#1

Updated by Bastian Waidelich over 9 years ago

Nice idea, but I'd prefer if those dependencies would be stored in the Package.xml as discussed before (for performance reasons those infos could be copied to PackageStates.php or similar during compile time).
We discussed this for the configuration dependencies (#28213), but IMO all dependencies should be stored at one place

Also available in: Atom PDF