Split adapters

[akerouanton]

Split adapters

https://php-and-symfony.matthiasnoback.nl/2014/04/theres-no-such-thing-as-an-optional-dependency/#the-solution

Why?

Currently, maintaining the whole adapters suite is tough:

• from time to time, tests break on some adapters and PRs (on another adapter) just can't be merged
• there're some risks of conflicting requirements between underlying SDKs (already happened! aws/aws-sdk-php v~2 dependency #426)
• some adapters should be deprecated and might be replaced by something else (e.g. Cache adapter)

Moreover there are some architectural problems:

• Big files are not properly handled (but Added stream feature to AwsS3 adapter.  #334 might be a good start)
• Metadata are not properly handled too
• Weird and/or duplicated behavior: Cache adapter & fileRegister in filesystem.
• Sometimes connection to external service is handled in the Adapter (e.g. FTP), sometimes it is not (e.g. AwsS3)
• Lack of proper exceptions Update AwsS3.php #395

How?

Split adapters across multiple repositories, then operate needed architectural changes.

TODO:

• Deprecate adapters we don't want to support anymore
  • AmazonS3
  • Cache (should be rewritten with PSR-16 in mind)
• Split every adapter in its own namespace and merge it in this branch,
  • AwsS3
  • AzureBlobStorage
  • DoctrineDbal
  • Dropbox
  • Flysystem
  • Ftp
  • GoogleCloudStorage
  • GridFS
  • InMemory
  • Local
  • MogileFS
  • OpenCloud
  • PhpseclibSftp
  • Sftp
  • Zip
• Merge every possible PRs on master, release the last version on this repository, and freeze the repository,
• Merge modifications from master into this branch,
• Push the core in its new repository, update every composer.json,
• Push every adapter in its new repository
• Plans for needed architectural changes

[akerouanton]

@flug @PedroTroller I've updated the description. What do you think?

[PedroTroller]

Do you keep the root repository with subtree system ?

[flug]

@NiR- You have a conflict with .travis.yml

[akerouanton]

@PedroTroller nope: I think the substree split would be useful only for splitting this repository the first time. After that there would be no more central repository.

@flug Yep, it's a WIP pull request/branch hence I don't really care of conflicts for now.