Add support for dependencies to TYPO3 Extensions without ext_emconf.php #541
Comments
DanielSiepmann
added a commit
to DanielSiepmann/fork-testing-framework
that referenced
this issue
Feb 14, 2024
The internal array always uses the extension key.
Not having an ext_emconf.php with dependencies to extension keys, but
only a composer.json with dependencies to package names will always
result in:
UnexpectedValueException: The package "extension_key" depends on "composer/package-key" which is not present in the system.
This is a common situation in modern TYPO3 projects where multiple
extensions are given which declare their internal dependencies to have
proper TYPO3 loading order.
A fallback from the dependency (which might be the composer name) to the
actual extension key is added.
Resolves: TYPO3#541
DanielSiepmann
added a commit
to DanielSiepmann/fork-testing-framework
that referenced
this issue
Feb 14, 2024
The internal array always uses the extension key.
Not having an ext_emconf.php with dependencies to extension keys, but
only a composer.json with dependencies to package names will always
result in:
UnexpectedValueException: The package "extension_key" depends on "composer/package-key" which is not present in the system.
This is a common situation in modern TYPO3 projects where multiple
extensions are given which declare their internal dependencies to have
proper TYPO3 loading order.
A fallback from the dependency (which might be the composer name) to the
actual extension key is added.
Resolves: TYPO3#541
DanielSiepmann
added a commit
to DanielSiepmann/fork-testing-framework
that referenced
this issue
Feb 15, 2024
The internal array always uses the extension key.
Not having an ext_emconf.php with dependencies to extension keys, but
only a composer.json with dependencies to package names will always
result in:
UnexpectedValueException: The package "extension_key" depends on "composer/package-key" which is not present in the system.
This is a common situation in modern TYPO3 projects where multiple
extensions are given which declare their internal dependencies to have
proper TYPO3 loading order.
A fallback from the dependency (which might be the composer name) to the
actual extension key is added.
Resolves: TYPO3#541
DanielSiepmann
added a commit
to DanielSiepmann/fork-testing-framework
that referenced
this issue
Feb 15, 2024
The internal array always uses the extension key.
Not having an ext_emconf.php with dependencies to extension keys, but
only a composer.json with dependencies to package names will always
result in:
UnexpectedValueException: The package "extension_key" depends on "composer/package-key" which is not present in the system.
This is a common situation in modern TYPO3 projects where multiple
extensions are given which declare their internal dependencies to have
proper TYPO3 loading order.
A fallback from the dependency (which might be the composer name) to the
actual extension key is added.
Resolves: TYPO3#541
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Does your feature request relate to a problem?
We removed all our
ext_emconf.phpfiles when updating from TYPO3 10 LTS to 12 LTS.This leads to issues like:
Describe the solution you would like
Provide native support for composer only projects with multiple TYPO3 extensions that declare their dependencies on each other (for loading order).
Optionally, describe alternatives you considered
One could keep ext_emconf.php.
The text was updated successfully, but these errors were encountered: