We have an artifact that specifies a dependency that we cannot automatically figure out the version to (likely due to unsupported parent POMs).
We would like to work around this by ignoring the bad dependency with excludedRuntimeDependencies, and then adding it back with extraDependencies, which will use the dependency version specified in the config file:
Context: https://github.com/xamarin/AndroidX/pull/773
We have an artifact that specifies a dependency that we cannot automatically figure out the version to (likely due to unsupported parent POMs).
We would like to work around this by ignoring the bad dependency with
excludedRuntimeDependencies
, and then adding it back withextraDependencies
, which will use the dependency version specified in the config file:However, the way we currently process this, the dependency gets excluded because the "excludes" are processed after the "extras".
Rework the logic so we run the "excludes" first and then add in the "extras".