TYPO3 Core

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...

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.

Patrik Karisch wrote:

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.

You're right, sorry. I thought this is only triggered when the package is active, but unfortunately that is not the case.

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

solved differently now :) No problems anymore.