Bug #65064
closed
composer error with multiple namespace definitions
0%
Description
Given I have "behat/behat":"*" in the require section of the composer file
And I do a composer update
And I go to the extension manager
Then I see the following exception
The Composer manifest of package "Behat.Behat" contains multiple namespace definitions in its autoload section but Flow does only support one namespace per package.
exeption id: 1348053245
Updated by Patrik Karisch over 9 years ago
- Target version set to next-patchlevel
Happens for 6.2.10 too. That's really annoying, so we can't use the new composer autoloading from typo3, when it chrashes for non-flow packages. If the EM want to analyse the composer.json of packages, then it should support all possible composer variant or don't crash on them...
Updated by Helmut Hummel over 9 years ago
- Status changed from New to Needs Feedback
This only happens if you activate the package manually (as there is no way to activate it in UI).
Can you explain to me, why you want to activate the package at all ?
Without composer class loading (pre 6.2.10) activating a composer package was not enough to make the classes of that available.
With composer class loading, activation is not necessary any more.
I'd rather not waste time fixing anything here in this area until we know if we need the concept of active/ inactive packages in the future.
Updated by Patrik Karisch over 9 years ago
Behat is not a package for activation. behat/behat is installed via composer and then located under Packages/Libraries. After issuing a composer install and then going into the extension manager (for doing other stuff, not activating behat) it crashes immediately with this extension. nothing is possible to do.
Updated by Helmut Hummel over 9 years ago
- Status changed from Needs Feedback to Accepted
Patrik Karisch wrote:
Behat is not a package for activation.
behat/behatis installed via composer and then located under Packages/Libraries. After issuing acomposer installand then going into the extension manager (for doing other stuff, not activating behat) it crashes immediately with this extension. nothing is possible to do.
You're right, sorry. I thought this is only triggered when the package is active, but unfortunately that is not the case.
Updated by Gerrit Code Review over 9 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37671
Updated by Helmut Hummel over 9 years ago
Please test the patch which is pushed to Review
Updated by Patrik Karisch over 9 years ago
Can I apply this patch to a 6.2.10 installation too?
Updated by Gerrit Code Review over 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37671
Updated by Gerrit Code Review over 9 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37671
Updated by Gerrit Code Review over 9 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37671
Updated by Benni Mack over 9 years ago
- Status changed from Under Review to Rejected
solved differently now :) No problems anymore.