Issue Bug Closed

#109580Letting out ext:backend as a composer dependency during extension testing fails "asset:publish"

Markus Klein 04/14/26, 16:51 updated 04/14/26, 19:05

Description

    "require": {
        "typo3/cms-core": "^13.4 || ^14@dev",
        "typo3/cms-extbase": "^13.4 || ^14@dev",
        "typo3/cms-fluid": "^13.4 || ^14@dev",
        "typo3/cms-frontend": "^13.4 || ^14@dev"
    },

using this composer.json and running composer update works with Core v13, but fails on v14 with:

> post-autoload-dump: TYPO3\CMS\Composer\Installer\Plugin->listen
Executing TYPO3 installer scripts
Executing "TYPO3\CMS\Composer\Plugin\Core\InstallerScripts\EntryPoint": 
Executing "TYPO3\CMS\Core\Composer\PackageArtifactBuilder": 
Executing "TYPO3\CMS\Core\Composer\ConsoleCommand": 
Executing command (CWD): '/usr/bin/php8.4' '-d' 'allow_url_fopen=1' '-d' 'disable_functions=' '-d' 'memory_limit=-1' '/var/www/.Build/vendor/bin/typo3' 'asset:publish'

In ServiceProviderCompilationPass.php line 166:

  [Exception (1550092654)]                                                     
  A registered extension for the service "backend.routes" requires the servic  
  e to be available, which is missing.                                         

Exception trace:
  at /var/www/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ServiceProviderCompilationPass.php:166
 TYPO3\CMS\Core\DependencyInjection\ServiceProviderCompilationPass->extendService() at /var/www/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ServiceProviderCompilationPass.php:97
 TYPO3\CMS\Core\DependencyInjection\ServiceProviderCompilationPass->registerExtensions() at /var/www/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ServiceProviderCompilationPass.php:61
 TYPO3\CMS\Core\DependencyInjection\ServiceProviderCompilationPass->process() at /var/www/.Build/vendor/symfony/dependency-injection/Compiler/Compiler.php:73
 Symfony\Component\DependencyInjection\Compiler\Compiler->compile() at /var/www/.Build/vendor/symfony/dependency-injection/ContainerBuilder.php:820
 Symfony\Component\DependencyInjection\ContainerBuilder->compile() at /var/www/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ContainerBuilder.php:146
 TYPO3\CMS\Core\DependencyInjection\ContainerBuilder->buildContainer() at /var/www/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ContainerBuilder.php:85
 TYPO3\CMS\Core\DependencyInjection\ContainerBuilder->createDependencyInjectionContainer() at /var/www/.Build/vendor/typo3/cms-core/Classes/Core/BootService.php:62
 TYPO3\CMS\Core\Core\BootService->prepareContainer() at /var/www/.Build/vendor/typo3/cms-core/Classes/Core/BootService.php:51
 TYPO3\CMS\Core\Core\BootService->getContainer() at /var/www/.Build/vendor/typo3/cms-core/Classes/Core/BootService.php:120
 TYPO3\CMS\Core\Core\BootService->loadExtLocalconfDatabaseAndExtTables() at /var/www/.Build/vendor/typo3/cms-core/Classes/Command/AssetPublishCommand.php:61
 TYPO3\CMS\Core\Command\AssetPublishCommand->execute() at /var/www/.Build/vendor/symfony/console/Command/Command.php:341
 Symfony\Component\Console\Command\Command->run() at /var/www/.Build/vendor/symfony/console/Application.php:1117

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.