WIP: Modulize OpenMage

[sreichel]

Description (*)

I wanted to modulize OM since a long time b/c you not always need every module. The only way was was/is to disbale in xml-config file or disable output via admin setting - but the code is still there.

How about having modules for erverthing (like M2)?

I have started this two years ago, but never finished. Now, working again on it, it seem to be nealy done.

This PR

• adds a ddev command (simple bash that can be used w/o ddev) to download all modules from my forked dev-project https://github.com/orgs/openmage-strict/repositories *
• adds a comoser executable script to update all files

Todo;

• automate ...
  • update after merger PR
  • tag new releases
• create new repo with sample composer.json

* some repos need be be restored after yesterday, but a working one ... https://github.com/openmage-strict/module-catalog

Related Pull Requests

• see Clean Adminhtml: Mage_Api blocks #4262

This PR targets to remove dependencies.

Manual testing scenarios (*)

1. run ddev openmage-mono -d to download all modules to .localdev/
2. run composer script to update to lateste version
3. ... to be done (commit/push/tag/...)

Questions or comments

How it works?

I have prepared every "Mage-module" and added ...

• composer.json (using requirements from xml-depends node).
• modma-fille

Once git-cloned all modules to .localdev run the composer script.

It reads the modman-file, search the files in any target-path (app/code,lib, ...) and copies back to .localdev/<moudule>.

All i have to to is to automate to push changes to single repos and tag releases when required.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud