[TYPO3-dev] Re: Set up new TYPO3 project with composer

[Philipp Wrann]

Tried to split it up using the composer includes section:

"includes" : {
"cms/composer.json" : {
"sha1":"ebfc077fc80cfe7f308925063162490aeb4237d5"
}
}

That worked partially, so it has been included, but the project was still instantiated in the root folder. There is a property called target-dir for composer.json but it is deprecated.

So includes may not fit for my case.

I also tried to add typo3 as package in repositories

"repositories" : [
{
"type": "package",
"package" : {
"name" : "typo3/cms",
"version": "7.3.0",
"source" : {
"url": "git://git.typo3.org/Packages/TYPO3.CMS.git",
"type": "git",
"reference": "dd60eaba7c6e44cafaa732603fb39e2dba694bf9"
}
}
}
]

But that way dependiencies are not resolved.

So i made some research, here is the script that creates the links etc... [1]
It is required by typo3/cms [2]
[1] https://github.com/TYPO3/CmsComposerInstallers/blob/master/Classes/TYPO3/CMS/Composer/Installer/CoreInstaller.php
[2] https://git.typo3.org/Packages/TYPO3.CMS.git/blob_plain/HEAD:/composer.json

And it does not look like it is configurable from that point.

So, one possibility would be to have independent composer setups for all purposes (what isnt really what i wanted to achieve) and put all of them in on git repository, the deployment needs to make multiple composer update processes etc.

Would you recommend not to do this?

Should i develop completely independent projects and develop/deploy them separately?