Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • T TYPO3.CMS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • accessibilityaccessibility
  • TYPO3.CMS
  • Repository
  • TYPO3.CMS
  • typo3
  • sysext
  • core
  • Classes
  • Package
  • ComposerDeficitDetector.php
Find file Blame History Permalink
  • Jochen Roth's avatar
    [TASK] Introduce composer manifest checks · ce34dbd7
    Jochen Roth authored Apr 15, 2021 and obartsch's avatar obartsch committed May 01, 2021
    The extension manager now provides a new module,
    which allows an integrator to display all available
    extensions with composer deficits, like missing
    composer.json or missing extension-key.
    
    The new module informs about the deficit and
    automatically generates a valid composer.json.
    proposal. In case no composer.json exists, the
    corresponding ext_emconf is sent to a new TER
    endpoint (https://extensions.typo3.org/composerize).
    This endpoint then generates a new composer.json
    proposal by resolving all dependencies.
    
    Furthermore, a new report is added to EXT:reports
    which also informs about such extensions by directly
    linking to the new EM module.
    
    This helps especially in non-composer-mode installations
    to ease the upgrade path for future TYPO3 versions which
    (hopefully) will rely on composer.json only for e.g.
    PackageStates.php.
    
    Resolves: #93931
    Releases: master, 10.4
    Change-Id: I1230363d5d03e03bff39e7070faf4e331532a292
    Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68778
    
    
    Tested-by: default avatarcore-ci <typo3@b13.com>
    Tested-by: default avatarBenni Mack <benni@typo3.org>
    Tested-by: default avatarOliver Bartsch <bo@cedev.de>
    Tested-by: default avatarJochen <rothjochen@gmail.com>
    Reviewed-by: default avatarBenni Mack <benni@typo3.org>
    Reviewed-by: default avatarHelmut Hummel <typo3@helhum.io>
    Reviewed-by: default avatarOliver Bartsch <bo@cedev.de>
    Reviewed-by: default avatarJochen <rothjochen@gmail.com>
    ce34dbd7