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?
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-onlyoption for example?