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're interested in this plugin for a multimodule repository that publishes library packages. We're looking for a way to turn relative dependency paths into proper package versions. The whole repo is monoversioned. We don't want to freeze third party dependencies and would like to keep defining supported dependency ranges for them. Would it be possible to support this use case with a --relative-only option for example?
The text was updated successfully, but these errors were encountered:
We're interested in this plugin for a multimodule repository that publishes library packages. We're looking for a way to turn relative dependency paths into proper package versions. The whole repo is monoversioned. We don't want to freeze third party dependencies and would like to keep defining supported dependency ranges for them. Would it be possible to support this use case with a
--relative-only
option for example?The text was updated successfully, but these errors were encountered: