[TYPO3-core] Composer name schema for TYPO3 CMS extensions

[Ernesto Baschny]

Fabien Udriot schrieb am 27.01.2014 10:46:

> I started a Note where to collect some info about Composer.
> https://notes.typo3.org/p/composer

Thanks for the work on that, Fabien. We have had this blueprint for the
Package Management in CMS in general:

http://wiki.typo3.org/Blueprints/Packagemanager

which I would also like to see updated with the information on the
naming conventions and composer specifics.

So if you and Tom, and others in this thread reach some conventions that
are relevant for CMS extension authors in future, please document them
in this blueprint also, so that it doesn't get lost in a notes document
(which is not searchable and linked anywhere).

Thanks!

Cheers,
Ernesto

> Some part could be added to the Blue Print or to the Wiki at one point.
> http://wiki.typo3.org/Blueprints/Packagemanager
> 
>     On the other topic: I thought the "typo3/" in the name was reserved for
>     official packages which would also use the "TYPO3" Vendor name. If you
>     are doing your own packages, you would use your own vendor name as a PHP
>     namespace and also in the vendor part of the composer "name". Maybe Tom
>     can clarify (and this needs to be properly documented yet!!!).
> 
> Ah! This is quite important. I overlooked the conventions related to
> namespaces
> <http://wiki.typo3.org/Namespaces#Does_and_don.27ts_for_developers>.
> Indeed, "TYPO3\CMS" is reserved for Core extensions and a different
> vendor name *must* be defined for a third-party extensions.
> 
> This vendor name must be reflected in the Composer file (and must not be
> "typo3/cms-" for third party extensions).
> 
> |{
>     "name":"vendor/package_name"
> }
> |
> 
> Thanks for your input.



-- 
Ernesto Baschny
TYPO3 CMS Core Developer
Release Manager TYPO3 4.5 & 6.2 LTS

TYPO3 .... inspiring people to share!
Get involved: typo3.org