-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make VCS plugins configurable #8556
Labels
downloader
About the downloader tool
enhancement
Issues that are considered to be enhancements
plugin
Topics related to ORT plugins
Comments
sschuberth
added
enhancement
Issues that are considered to be enhancements
downloader
About the downloader tool
plugin
Topics related to ORT plugins
labels
Apr 23, 2024
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 10, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., revision, recursive) and should support implementation-specific configurations that are unique to each VCS. This refactoring encapsulates common configurations as attributes of a `VersionControlSystemConfiguration` data class, while implementation-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556 Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 10, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support implementation-specific configurations that are unique to each VCS. This refactoring encapsulates common configurations as attributes of a `VersionControlSystemConfiguration` data class, while implementation-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556 Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 10, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support implementation-specific configurations that are unique to each VCS. This refactoring encapsulates common configurations as attributes of a `VersionControlSystemConfiguration` data class, while implementation-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556 Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 11, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support implementation-specific configurations that are unique to each VCS. This refactoring encapsulates common configurations as attributes of a `VersionControlSystemConfiguration` data class, while implementation-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556 Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 11, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support implementation-specific configurations that are unique to each VCS. This refactoring encapsulates common configurations as attributes of a `VersionControlSystemConfiguration` data class, while implementation-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556 Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 11, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support implementation-specific configurations that are unique to each VCS. This refactoring encapsulates common configurations as attributes of a `VersionControlSystemConfiguration` data class, while implementation-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556 Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 21, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 21, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 22, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 23, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 23, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 23, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 29, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 4, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 4, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 7, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 7, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 8, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 8, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 8, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 11, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. This refactoring keeps the common configurations attributes as they are, while VCS-specific configurations are stored generically in an `options` attribute. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 11, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 11, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 13, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 13, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 13, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 13, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 21, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. The effects are limited to usage through the command-line interface of the Downloader tool, designed primarily for scripted operations. In other stages of the ORT pipeline these configuration options have no effect. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Nov 21, 2024
While VCS implementations are already plugins, they are not yet configurable. VCS implementations require common configurations (e.g., `revision`, `recursive`) and should support also VCS-specific configurations if they are consumed via their API. This allows to add functionality to individual VCS implementations without the need to implement them for all of them. The effects are limited to usage through the command-line interface of the Downloader tool, designed primarily for scripted operations. In other stages of the ORT pipeline these configuration options have no effect. Fixes oss-review-toolkit#8556. Signed-off-by: Wolfgang Klenk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
downloader
About the downloader tool
enhancement
Issues that are considered to be enhancements
plugin
Topics related to ORT plugins
While VCS implementations already are plugins, they are not configurable yet. As VCS both require configs that are common to all VCS implementations, e.g.
ort/downloader/src/main/kotlin/VersionControlSystem.kt
Lines 166 to 169 in d53ac0b
but should also be able to get implementation-specific configuration, probably an approach like with
PackageManagerConfiguration
would be feasible.Having such configuration would probably help to address the following related issues
Tasks
The text was updated successfully, but these errors were encountered: