Open mandelsoft opened 2 months ago
This PR exceeds the recommended size of 10000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
VIOLATION DESCRIPTION | NUMBER OF VIOLATIONS |
---|---|
HIGH/CRITICAL SECURITY VULNERABILITIES | 3 |
MAJOR UPDATES AVAILABLE | 0 |
LICENSE REQUIRES REVIEW | 1 |
HIGH RISK LICENSES | 10 |
RESTRICTIED LICENSE FOR ON-PREMISE DELIVERY | 0 |
Integration Tests for 862458c1dc8b515770b0ca6004fcff94bee93322 run with result: Success ✅!
This PR exceeds the recommended size of 10000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
Integration Tests for 49a79ea7431fb631cf34fcda3a41856f1637ad3c run with result: Success ✅!
This PR exceeds the recommended size of 10000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
Integration Tests for 49a79ea7431fb631cf34fcda3a41856f1637ad3c run with result: Success ✅!
Integration Tests for 1ba6e56295aa2c17496f80160e71b2d9d9cd158b run with result: Success ✅!
Integration Tests for e76ec98cef5250d900ffabb9d946097978a87f54 run with result: Success ✅!
This PR exceeds the recommended size of 10000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
Integration Tests for 02592a6e221518a0d045bc1a28a1bce5fecd5e61 run with result: Success ✅!
This PR exceeds the recommended size of 10000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
Integration Tests for 58304543654219e16b46ca283b661fed4b5b1ba5 run with result: Success ✅!
This PR exceeds the recommended size of 10000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
Integration Tests for 58304543654219e16b46ca283b661fed4b5b1ba5 run with result: Success ✅!
Description
Restructure the ocm core library according to the intended new package structure. In a first step we keep the module name
github.com/open-component-model/ocm
and stay in this repository.The actual first migration step has been be done based on the original main branch just by calling
migrate.sh --paths
from the repository root folder. It can be repeated for new main versions.Afterwards it is possible to call
make build
make generate
make test
make generate-deepcopy
go fmt ./{api,cmds}/...
make check
These commands should succeed.
This is the current state. Everything else is not yet done. So far, packages are moved and renamed to their intended location in the package structure. The used relative paths should be adapted and tsts and component builds are runnig.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Screenshots
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist: