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

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

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

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

Without ext_emconf ordering of loaded extension in tests is important.
There is already an issue about this topic on:
TYPO3/testing-framework#541

Without ext_emconf ordering of loaded extension in tests is important.
There is already an issue about this topic on:
TYPO3/testing-framework#541

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

The testing-framework internal composer package management
used to determine source location of extensions to provide
them in the functional test instances (legacy mode) stores
extension packages in internal property state by the TYPO3
extension key. In case `ext_emconf.php` does not exist in
a extension, the fallback determined it by normalizing the
package name from the composer name or used the basename
of the source location folder as extension key.

The fallback logic was based on the need to allow loading
functional test fixture extension.

TYPO3 extension are sensitive to loading order which is
determined in different ways depending on the installation
mode. To mimic the TYPO3 core legacy mode sorting, custom
package sorting has been added to the testing-framework,
which has to deal with the fact that extension may not
provide a `ext_emconf.php` anymore, which is not needed
for composer installations.

Extension depending on another extension failed to be
sorted correctly with following exception:

    UnexpectedValueException: The package "extension_key"
    depends on "composer/package-key" which is not present
    in the system.

The root cause for this is the fact, that the composer.json
entry for the `extension-key` has not been used as first
source when reading extension from the filesystem. With this
change, places dealing to determine extension key from package
now respects the composer.json extension-key as first source.

Resolves: #541

The testing-framework internal composer package management
used to determine source location of extensions to provide
them in the functional test instances (legacy mode) stores
extension packages in internal property state by the TYPO3
extension key. In case `ext_emconf.php` does not exist in
a extension, the fallback determined it by normalizing the
package name from the composer name or used the basename
of the source location folder as extension key.

The fallback logic was based on the need to allow loading
functional test fixture extension.

TYPO3 extension are sensitive to loading order which is
determined in different ways depending on the installation
mode. To mimic the TYPO3 core legacy mode sorting, custom
package sorting has been added to the testing-framework,
which has to deal with the fact that extension may not
provide a `ext_emconf.php` anymore, which is not needed
for composer installations.

Extension depending on another extension failed to be
sorted correctly with following exception:

    UnexpectedValueException: The package "extension_key"
    depends on "composer/package-key" which is not present
    in the system.

The root cause for this is the fact, that the composer.json
entry for the `extension-key` has not been used as first
source when reading extension from the filesystem. With this
change, places dealing to determine extension key from package
now respects the composer.json extension-key as first source.

Resolves: #541
Releases: main, 8

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