#108345Make it possible to omit ext_emconf.php in classic mode
Description
ext_emconf.php is still required for proper dependency resolving of installed extensions.
Provide a different way for PackageManage to distinguish required TYPO3 extension from required
Composer packages
Reviews 8
- 14.3 95566[TASK] Update composer.json when downloading extensions from TER
- main 93487[TASK] Update composer.json when downloading extensions from TER
- main 94310[!!!][TASK] Throw on extensions with incomplete composer.json
- main 93611[BUGFIX] Migrate ext_emconf.php "state" to package metadata
- main 93618[BUGFIX] Respect `suggests` package constraints
- main 93531[WIP][BUGFIX] Disarm `ext_emconf.php` deprecation for functional tests
- main 93530[BUGFIX] Avoid `Undefined property: stdClass::$version` warning
- main 91908[FEATURE] Allow extensions to move ext_emconf.php info to composer.json
Related issues 7
- Bug #109357Testing framework broken after merge of #108345
- Bug #109434Improve deprecation message for ext_emconf.php
- Bug #109473`Undefined property: stdClass::$version` warning `PackageManager`
- Bug #109482Allow declaring version in composer.json by a custom field in composer.json extra
- Bug #109485LanguagePackService still reads ext_emconf.php while rest of core uses composer.json
- Bug #109552Package sorting doesn't take `suggested` packages into account anymore
- Task #109993Throw on extensions with incomplete composer.json