Project

General

Profile

Actions

Bug #70175

closed

Cannot fetch version of extensions having a composer.json file

Added by Xavier Perseguers about 9 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
composer
Target version:
-
Start date:
2015-09-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
hard
Is Regression:
No
Sprint Focus:

Description

When an extension features a composer.json file, and according to best practices from Helmut (https://github.com/helhum/ext_scaffold), the version should not be present but inferred from a corresponding Git tag.

When having an extension, in TYPO3 6.2 at least, which has a composer.json and the standard ext_emconf.php (e.g., EXT:restdoc), Extension Manager is solely relying on composer.json for extracting the metainformation. This leads to incomplete information since the version is not found. It does not matter much until one tries to read the version number using the API:

$version = \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getExtensionVersion(“restdoc”);

// BANG!
// #1395614959: Version number in composer manifest of package "restdoc" is missing or invalid

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #70149: Dependencies are not resolved correctly.RejectedNicole Cordes2015-09-28

Actions
Has duplicate TYPO3 Core - Bug #72631: Version number in composer manifest is missing or invalidClosed2016-01-11

Actions
Actions

Also available in: Atom PDF