Details
-
Task
-
Status: Closed
-
Trivial
-
Resolution: Fixed
-
None
-
None
-
None
-
New
Description
Palantir's version control plugin clashes with POM generation for some reason and POMs have superfluous entries in dependencyManagement section. While this should not hurt (in theory), I found it does cause problems for downstream dependencies (locks versions and requires manual intervention).
POMs should be published with just the dependencies actually used. I do have an (ugly) workaround for this - will fix it tomorrow.
[1] https://github.com/palantir/gradle-consistent-versions/issues/550