Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More explanations about the composer.json given as example #5

Open
fabarea opened this issue Feb 5, 2014 · 1 comment
Open

More explanations about the composer.json given as example #5

fabarea opened this issue Feb 5, 2014 · 1 comment

Comments

@fabarea
Copy link

fabarea commented Feb 5, 2014

On the README.md file, a composer.json file is given as example. Though, I am not sure to understand well the reason why to add lw/typo3-installers as requirement and the composer.lightwerk.com repository in the composer file. Doesn't it work without as demoed on http://composer.lightwerk.com/? What would be the benefit?

@AndreasA
Copy link

AndreasA commented Oct 6, 2014

Actually with typo3 6.2 I do not think one should use the lightwerk composer.json at all for an extension. That only works good for the lightwerk typo3-ter downloads but the extension itself should use "type": "typo3-cms-extension" and no require at all.
That will use the "composer/installers" (which should be loaded first without any additional require) and also install to the typo3conf/ext directory.
Furthermore, that way typo3 recognizes the extension as a typo3 extension and uses the directoryname as extension key as before and not vendorname.extkey which would create problems if you somewhere try to access the directory name as extension key.

Furthermore, for composer one should add a replace with only the extension key, that way if I were to define a extension as requirement somewhere composer would accept it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants