Details
-
Improvement
-
Resolution: Unresolved
-
High
-
None
-
None
-
None
Description
Since eZ Legacy installs its own composer.json at the (LS) root folder, and it is not possible to have a user-defined composer.json added to it, it is difficult for end users to add their own per-project composer.json (if they modify the existing one from eZ, it will be overwritten on updates).
A proposed solution:
- allow users to create a composer.json file in the parent directory of where eZ will be installed
- in that composer.json, they can specify that they depend on eZ, the desired directory for ez to be installed in, and any other extra dependencies