[Improvement]: support multiple composer.lock files #12441
Replies: 5 comments 4 replies
-
how do you differentiate between composer.dev.local.json and composer.json? As far as composer is concerned, that is not a "standard" use-case. |
Beta Was this translation helpful? Give feedback.
-
You can add The official composer repository is actually were I got the idea from: someone else wanted pretty much the same setup, so the guys from composer suggested this approach. I agree, though, it doesn't really seem to be a common use case. Would you like to share your approach on bundle development across your team? |
Beta Was this translation helpful? Give feedback.
-
We either develop the bundle directly inside the project using local directories with composer:
Or we develop the bundle completely independent with tests and stuff and include it in the project like a regular dependency. |
Beta Was this translation helpful? Give feedback.
-
I just had another look at this and am wondering if @brusch knows why the UpdateUsing only the following lines, everything works as expected: pimcore/lib/Composer/PackageInfo.php Lines 68 to 71 in a020f96 |
Beta Was this translation helpful? Give feedback.
-
@dpfaffenbauer thank you for sharing - much appreciated! We too developed bundles within the projects, but that lead to many accidental dependencies to the The second approach is pretty much what I'm trying to achieve. Only that the bundle is supposed to be in another, internal project, which can be deployed whenever a new feature was implemented. This way, we can directly showcase new features and raise awareness of any available functionality. |
Beta Was this translation helpful? Give feedback.
-
Improvement description
Description
It would be nice to be able to define the
composer.lock
file that is used for loading the available composer bundles, used here:pimcore/lib/Composer/PackageInfo.php
Line 62 in a020f96
Preferably, as option for the
bin/console pimcore:bundle:enable
command - unless, anyone has a better idea.Details
Developing locally, our setup requires multiple composer files:
composer.json
, which will require any released bundle, so it is available in our developer-sandbox to interactively showcase what they are used for and how to use them.composer.dev.local.json
, which is used to add repositories as@dev
, so they are symlinked by composer (using therepositories
section) for local development.However, one cannot enable the bundle using
bin/console pimcore:bundle:enable <bundle-name>
, because only thecomposer.lock
file is considered, which does not contain the bundle just yet.Beta Was this translation helpful? Give feedback.
All reactions