Use the composer.json example on windows. In Addition to the composer manifest we provide a LocalConfiguration.php and AdditionalConfiguration with our provisioning. So the bootstrap is not in FIRST_INSTALL mode, maybe that's something that does have an influence? When we hit typo3/install to run DB compare to seed the database we do get:
Fatal error: Uncaught exception 'LogicException' with message 'No class loading information found for TYPO3 CMS. Please make sure you installed TYPO3 with composer or the typo3/contrib/vendor folder is present.' in ....
Note to self:
- check wether dropping provisionde typo3conf/* items and adding FIRST_INSTALL does make a change
- check wether targeting dev-master does make a change
- check wether the autoload is created, where it is created and check the content
see http://composer.typo3.org/
composer create-project typo3/cms-base-distribution CmsBaseDistribution dev-master
executed under Linux
[RuntimeException]
Could not scan for classes inside "/tmp/foo/CmsBaseDistribution/typo3_src/typo3/sysext/core/Resources/PHP/" which does not appear to be a file nor a folder
Downloading a .zip/.tgz release package we can see composer.json with vendor-dir set to typo3/contrib/vendor (in order to package the vendor packages into the release).
Ok, so now let's try to set the vendor-dir to typo3/contrib/vendor ourselves, see composer-vendor-dir-contrib.json
"vendor-dir": "typo3/contrib/vendor",
[InvalidArgumentException]
The symlink target "typo3" already exists
I have checked for permissions and everything else.... Linux plus Mac are tested and working fine... I updated the gist to be more precise and contain example composer manifests. Note we are currently targeting 7.3.1. Will test dev-master tomorrow, also the example with the create-project command should target master anyway....and is failing as well on (my) linux