Skip to content

Support multiple license sources#4527

Draft
oheger-bosch wants to merge 2 commits intoeclipse-apoapsis:mainfrom
boschglobal:oheger-bosch/multiple_license_sources
Draft

Support multiple license sources#4527
oheger-bosch wants to merge 2 commits intoeclipse-apoapsis:mainfrom
boschglobal:oheger-bosch/multiple_license_sources

Conversation

@oheger-bosch
Copy link
Contributor

This PR implements a solution for #4185: To support multiple license sources in rule violations in the API and the UI. It uses the approach to introduce a new licenseSources property in the data model, keeping the old one to not break the API and older clients.

In the UI, the license sources are displayed as comma-delimited list. If you want a more sophisticated design, I am out:
rule_violations

This is a follow-up for [1]. It extends the API model to handle multiple
license sources for a rule violation which is now supported by ORT.

Add a new property `licenseSources` to avoid breaking clients that can
still use the old `licenseSource` property.

[1]: eclipse-apoapsis#4181

Signed-off-by: Oliver Heger <oliver.heger@bosch.com>
Display all license sources for rule violations that are now returned by
the API.

Fixes eclipse-apoapsis#4185.

Signed-off-by: Oliver Heger <oliver.heger@bosch.com>
@github-actions
Copy link

Issues referenced in commit messages and issues linked to this PR are not in sync.
Please manually link this PR to the following issues: 4185

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments