Do not define scope for dependencyManagement entries The semantics between the scope of a constraint in Gradle and the scope of a declaration in dependencyManagement in Maven are fundamentally different. Given this, Gradle will no longer attempt to define a scope for dependencyManagement entries when creating POM files. The only exception is the import scope as it carries special meaning.
Add validation at publication time This commit introduces validation when generating Gradle Module Metadata:
- check that there's at least one variant published - each variant must have at least one attribute - there shouldn't be duplicate variant names - each variant must have a different (attributes,capabilities) combination