TYPO3 Core

The filenames of datasets for tests are pretty long, which makes it likely for them to exceed the maximum path length on windows.
Thus, causing it to be a real PITA to install Typo3 CMS via composer, for example when using vagrant on windows:

 [PharException]
 Extraction from phar "/vagrant/www/typo3test/html/typo3_src/e5e49e9051486449bfaa
 5e842a3a71ea.14" failed: Cannot extract "typo3_src-6.2.14/typo3/sysext/workspace
 s/Tests/Functional/DataHandling/IRRE/ForeignField/PublishAll/DataSet/createNLoca
 lizeParentContentNHotelNOfferChildrenNDiscardCreatedParent.csv", could not open
 for writing "/vagrant/www/typo3test/html/../Packages/Libraries/composer/9ef9abf2
 /typo3_src-6.2.14/typo3/sysext/workspaces/Tests/Functional/DataHandling/IRRE/For
 eignField/PublishAll/DataSet/createNLocalizeParentContentNHotelNOfferChildrenNDi
 scardCreatedParent.csv" 

Or when running composer directly from the windows host:

 [PharException]
 Extraction from phar "D:/vagrantbox/ubuntu-server-14-LTS/www/typo3test/html
 /typo3_src/355afb22645d419fbaca5944eb78270a.14" failed: Cannot extract "typ
 o3_src-6.2.14/typo3/sysext/workspaces/Tests/Fun..." to "D:\vagrantbox\ubunt
 u-server-14-LTS\www\typo3test\h...", extracted filename is too long for fil
 esystem

Of course, you could argue that the initial path to the document root is just too long and should be shorter. But there are still some really long paths, forcing you to use extremely short directory names - which basically makes it impossible to install the project directly to the shared directoy of the VM. As a workaround, you can install/update it further up on the hard drive, reducing the path length, then moving it to the actual document root.

But this is a pretty inconvenient way of maintaining your projects. Although this is not directly caused by typo3 but rather by the OS, is there any chance that the filenames could be at least shortened in some extend? (If you have any other solution, that would be fine by me.)

I've done some search for the most critical files that are causing problems for me:

./typo3_src/typo3/sysext/impexp/Tests/Functional/Import/PagesAndTtContentWithImages/DataSet/Assertion/importPagesAndRelatedTtContentWithImagesBut
WithoutStorageOnCaseInsensitiveFilesystems.csv
./typo3_src/typo3/sysext/impexp/Tests/Functional/ImportFromVersionFourDotFive/PagesAndTtContentWithRteImagesAndFileLink/DataSet/Assertion/importP
agesAndRelatedTtContentWithRteImagesAndFileLink.csv

Followed up by (more than 180 characters in path):

./typo3_src/typo3/sysext/impexp/Tests/Functional/Import/PagesAndTtContentWithImages/DataSet/Assertion/importPagesAndRelatedTtContentWithImagesBut
WithoutStorageOnCaseInsensitiveFilesystems.csv
./typo3_src/typo3/sysext/impexp/Tests/Functional/Import/PagesAndTtContentWithImages/DataSet/Assertion/importPagesAndRelatedTtContentWithImagesBut
WithoutStorageOnCaseSensitiveFilesystems.csv
./typo3_src/typo3/sysext/impexp/Tests/Functional/ImportFromVersionFourDotFive/GroupFileAndFileReferenceItemInFlexForm/DataSet/Assertion/importGro
upFileAndFileReferenceItemInFlexForm.csv
./typo3_src/typo3/sysext/impexp/Tests/Functional/ImportFromVersionFourDotFive/GroupFileAndFileReferenceItemInFlexForm/ImportExportXml/impexp-grou
p-file-and-file_reference-item-in-ff.xml
./typo3_src/typo3/sysext/impexp/Tests/Functional/ImportFromVersionFourDotFive/PagesAndTtContentWithRteImagesAndFileLink/DataSet/Assertion/importP
agesAndRelatedTtContentWithRteImagesAndFileLink.csv
./typo3_src/typo3/sysext/impexp/Tests/Functional/ImportFromVersionFourDotFive/PagesAndTtContentWithRteImagesAndFileLink/ImportExportXml/pages-and
-ttcontent-with-rte-image-n-file-link.xml

regards
Thomas