#57216EM fails to resolve dependency requirement when dependency's composer.json lacks version
Description
As subject describes, this is an edge case which happens only when:
- Extension A depends on Extension B
- Extension B is currently installed
- Extension A is not currently installed
- Extension B has composer.json file
- Extension B composer.json file contains no “version” attribute or this attribute is empty.
Failure in EM: Unable to resolve dependency for “$dependencyExtension” even if ext_emconf.php of Extension B has proper version.
Cause: DependencyUtility uses ExtensionManagementUtility::getExtensionVersion when dependency extension IS installed, this method then relies on PackageMetaData which only supports composer.json.
Suggested action: Throw Exception from within ExtensionManagementUtility::getExtensionVersion() if version value from PackageMetaData is empty.