Actions
Bug #84620
closedPackage symfony/finder 4.0.7 might break composer installation
Status:
Closed
Priority:
Must have
Assignee:
-
Category:
composer
Target version:
-
Start date:
2018-04-04
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
8
PHP Version:
7.1
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
I updated the symfony/finder package in a TYPO3 8.7.12 installation to 4.0.7. Now I cannot install composer packages that are included via path.
Steps to reproduce:
- Setup a TYPO3 8.7 composer installation
- Create a folder named "packages" in your project
- Create an example extension named "test_extension" inside the packages folder with a composer.json file.
- Add a repository to the projects composer.json with type path and url packages/*
- Require your extension in your projects composer file
- Move to the Extension Manager in the TYPO3 backend. The new extension will not be there.
The reason is, that with symfony/finder 4.0.7, that generated package path is the path to the original folder (packages/test_extension) and not the path to the typo3cond/ext/test_extension folder.
This might be a problem with symfony/finder package but I open a ticket here to help people having this problem. Is solved it by requiring symfony/finder 4.0.6 again.
Updated by Wouter Wolters over 6 years ago
- Status changed from New to Needs Feedback
Hi, I think this was solved 6 hours ago with https://forge.typo3.org/issues/84601
Can you confirm?
Updated by Tim Schreiner over 6 years ago
Oh sorry, didn't see that when searching forger. I think that's a duplicate then.
Updated by Stephan Großberndt over 6 years ago
- Status changed from Needs Feedback to Closed
Updated by Stephan Großberndt over 6 years ago
- Is duplicate of Bug #84601: Installation fails with "extbase" not found exception added
Actions