Project

General

Profile

Actions
Copy link

Bug #60863

closed

EXT with composer.json and depends on other ext (from e.g. typo3-ter) in composer.json fails if EXT does not have composer.json

Added by Andreas Allacher over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-08-08
Due date:
% Done:

0%

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

Description

If I want to setup my whole project using composer and include a composer.json in my custom extensions and add the corresponding dependencies there,
e.g. other extensions then the installation will fail EVEN if the other extension was installed via composer.json of the main project.
The reason is that the other extension does not itself have a composer.json, so PackageManagement seems to look for an extension with the corresponding composer name but cannot find it.
However, in the PackageStates.php there actually is a 'composerName' property that was set correctly but the requirement fails.

I hope what I mean is understandable.

Also if an extension has a composer.json with external libraries as requiements then the installation seems to fail too, does the external library have to be installed at a specific path so that it can be found? Shouldn't it be automatically retrieved?

Actions
Copy link

Also available in: Atom PDF