[TYPO3-dev] [TYPO3 7.4] exception in EM when using a composer dependency to a third party package

[Helmut Hummel]

Hi!

Franz Koch wrote:
> Hey guys,
>
> I'm struggling a little with the upgrade to 7.4 and a extension that has
> dependency to a third party package which is NO Typo3 extension.
>
> In my case I'm having a LESS parser extension that's having
> "oyejorge/less.php" as dependency in composer.json and I get this
> exception when going to the ExtensionManager.
>
> ---------------
> #1382276561: The package "ws_less" depends on "oyejorge/less.php" which
> is not present in the system. (More information)
> ---------------
>
> I suppose this is a bug in the dependency resolver?

Yes and no.

First of all, the extension manager of course cannot resolve 
dependencies to composer packages. Because of that, you cannot just add 
such a dependency to your composer.json of your extension, upload it via 
EM end expect it to work.

However, if you use composer to set up your project and use such an 
extension, composer will resolve your dependencies correctly. In that 
case however, you should not go to the extension manager and add (more) 
extensions there but should just use composer.

That said, there is still a thing which does not work currently and this 
is activating an extensions, so that TYPO3 incudes all extension files 
and sets up DB tables if needed.

There are a few things missing here. First:

https://review.typo3.org/#/c/42615/

Which basically makes the PackageManagement ignore composer dependencies.

And secondly, we need a way to write the package states file upon 
composer install/update.

Lastly, we need a way to activate an extension without influencing the 
package states file.

All these missing pieces will be implemented soon.

Kind regards,
Helmut

-- 
Helmut Hummel
Release Manager TYPO3 6.0
TYPO3 CMS Active Contributor, TYPO3 Security Team Member

TYPO3 .... inspiring people to share!
Get involved: typo3.org