[FLOW3-general] Package handling / autoloading

[Robert Lemke]

Hi folks,

just a few, brief thoughts on this topic:

In general I'd like the package management to switch to Composer as far as possible. If we can switch to Composer packages all together without noteworthy hassle for the developers of existing FLOW3 packages, we should do that.

So, if technically possible, we should provider Composer.json files for all of the packages we maintain. The code which handles FLOW3 packages separately should only be kept for BC reasons. We might even generate a Composer.json file for those packages which don't have one yet. If viable, we should also get rid of the Meta/Package.xml.

Apart from that, our package management should not, in my opinion, introduce non-trivial features (like special class loading rules) which are not compatible with Composer.

I think that we should take the opportunity and make some buzz about FLOW3's - and also TYPO3's - Composer support at the time we release it. Jordi will certainly appreciate such a campaign and spread the word which can give additional attention to TYPO3 / FLOW3.

Does that make sense to you? Can you derive some practical decisions from it?

Greetings from some gap between conferences,

Robert

-- 
Robert Lemke
Lead Developer TYPO3 Phoenix and FLOW3
Co-Founder TYPO3 Association

Blog: robertlemke.de/blog
Get involved: typo3.org – flow3.org