You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently manually configuring per package which repo it should come from. Usually right after the release of a possible platform (e.g. Leap 15.4) we start with just 3 repositories, but as soon as updates are released, more repos are needed and therefore frequent manual config changes. Instead, for a given distribution obs-to-maven could consider all relevant channels repositories and automatically select the available package with the highest version number? The configuration would be simplified overall, as the repo per package option would become optional (only needed to force a specific repo / lower version).
The text was updated successfully, but these errors were encountered:
We are currently manually configuring per package which repo it should come from. Usually right after the release of a possible platform (e.g. Leap 15.4) we start with just 3 repositories, but as soon as updates are released, more repos are needed and therefore frequent manual config changes. Instead, for a given distribution
obs-to-maven
could consider all relevantchannelsrepositories and automatically select the available package with the highest version number? The configuration would be simplified overall, as the repo per package option would become optional (only needed to force a specific repo / lower version).The text was updated successfully, but these errors were encountered: