move "CORE" to own package

[jkowalleck]

see https://github.com/CycloneDX/cyclonedx-php-composer/milestone/5

impact

as long as all interfaces/namespaces stay untouched, this would not be a breaking change.

The new external package/library is a one-to-one copy of the original code from this project, which now is a dependency/required of this project. So usage/leverage of the original code is still possible without any changes for third parties.

benefit:

• core can evolve independently from the plugin: features/bugfixes are independent from plugin's release cycle

acc / crit:

• non-composer-plugin-namespaces are removed from psr4 autoloader - via removed core lib from src #127
• non-composer-plugin-classes(all not in folder src/Composer ) are moved to an own package, that is required by the plugin - via removed core lib from src #127

---

steps in order

1. create new repo see https://github.com/CycloneDX/cyclonedx-php-library
2. copy the code to new repo & test it
3. make repo a composer package
4. publsh at https://packagist.org
5. tag the new package
6. remove now "external"/duplicated files from plugin-repo - via removed core lib from src #127
7. require the new package in the plugin package with an appropriate version range - via removed core lib from src #127
8. have the usage as a lib merged to master

---

possible followups: / ideas for the extracketd package:

• rename namespace CycloneDX\Core\Serialize to CycloneDX\Core\Serialization -- moved to rename some namespaces  cyclonedx-php-library#5
• rename namespace CycloneDX\Core\Validate to CycloneDX\Core\Validation -- moved to rename some namespaces  cyclonedx-php-library#5
• Json normalizers returns object of stdClass instead of associative arrays -- see JSON normalizers returns object instead of associative arrays cyclonedx-php-library#4
  • therefore revisit the serialisers in general and simplify them !