Project

General

Profile

Actions

Bug #84620

closed

Package symfony/finder 4.0.7 might break composer installation

Added by Tim Schreiner over 6 years ago. Updated over 6 years ago.

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:

  1. Setup a TYPO3 8.7 composer installation
  2. Create a folder named "packages" in your project
  3. Create an example extension named "test_extension" inside the packages folder with a composer.json file.
  4. Add a repository to the projects composer.json with type path and url packages/*
  5. Require your extension in your projects composer file
  6. 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.


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #84601: Installation fails with "extbase" not found exceptionClosed2018-04-04

Actions
Actions

Also available in: Atom PDF