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
0%
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?
Updated by Andreas Allacher about 10 years ago
Just removing the vendor name in the require section and adding a replace without the vendor name for extensions with composer.json does the trick (and also using require without the extension).
The second is to ensure it works no matter if I use the non composer key in the PackageStates.php too.
Updated by Peter Niederlag over 9 years ago
- Status changed from New to Needs Feedback
Is the problem solved or does it still need a fix?
To me it seems all TYPO3 CMS extensions need a replace for the extension key without the vendor prefix in their composer.json anyway
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.