Composer requirement to package that is not type=typo3-cms-extension
Not sure wether this behaviour is a bug or a missing feature or mis-configuration on my side.
I could not find a hint in the 8.x changelog documentation by searching for "composer", "depend", "package".
In TYPO3 8.3.1 in extension manager. A extension of type "typo3-cms-extension" exists and is required and installed via composer as composer package. That extension itself brings a requirement to further composer packages not of type "typo3-cms-extension". When pressing button "activate". A Exception is thrown in 8.3.1 in Extension Manager:
"#1382276561: The package "XXX" depends on "YYY" which is not present in the system. (More information)"
A demo package composer file could be
The exception is only thrown in extension manager.
This exception is not thrown when the extension is activated via EXT: typo3_console.
#1 Updated by Felix Kopp almost 3 years ago
Follow the composer.json specs from http://insight.helhum.io/post/148886148725/composerjson-specification-for-typo3-extensions as well.
#2 Updated by Mathias Schreiber almost 3 years ago
I am pretty certain this is a bug.
I guess the EM treats composer.json files of an extension the same way as ext_emconf.php files, thus not resolving the dependencies outside of typo3conf/ext.
One question though.. you did not mention whether the dependency itself got installed, but since I guess you installed the extension via composer those dependencies were resolved correctly, right?
#3 Updated by Felix Kopp almost 3 years ago
Yes, everything "below" typo3 / in composer went through without problems: Libraries are downloaded and auto-loaded within vendor directory.
Also the activation of the extension works just fine without exceptions when done via typo3_console.
Seems like the source for this problem lies within the EM.
#9 Updated by Helmut Hummel about 2 years ago
- Status changed from Under Review to Needs Feedback
Hm, ok, the fix isn't easy.
I would go for the advice that constriants section in ext_emconf.php is mandatory and maybe throw a better exception if it is not present, but composer.json requirements exist