Closed quaff closed 2 years ago
As described in the documentation, customization of the pom can already be disabled.
👍 Great!
Could we check if versionMapping
present then disable it by default?
While I think that would be technically possible, I would prefer not to add the complexity that it would bring both in terms of the code and in the behaviour of the configuration option. For example, what would happen if customization of the pom has been explicitly enabled yet every dependency has a version?
While I think that would be technically possible, I would prefer not to add the complexity that it would bring both in terms of the code and in the behaviour of the configuration option. For example, what would happen if customization of the pom has been explicitly enabled yet every dependency has a version?
Only set the default enabled
to false
if versionMapping
of MavenPublication
present, if user set enabled
explicitly, respect it no matter true
or false
.
Thanks for the suggestion, but as I said above, I don't want to add the complexity.
https://docs.gradle.org/current/userguide/publishing_maven.html#publishing_maven:resolved_dependencies Gradle supports resolving version for every dependency now, then the
<dependencyManagement/>
is superfluous, Currently I need to remove it inpom.withXml {}
.