Julian>Do you propose to remove pom.xml files from git Of course I do. I just thought "migrate Maven to Gradle" to mean "we fully replace Maven with Gradle", not like "we add Gradle build scripts and support two build systems at the same time".
Julian>generate them upon release Gradle can generate the files automatically. It works with current PR104 state it is generated before the jars are pushed to Nexus, and one can easily to generate pom file (e.g. gw generatePomFileForCorePublication or gw publishToMavenLocal) Here's how a basic pom information is declared (e.g. name, description, licenses, etc, etc): https://github.com/vlsi/calcite-avatica/blob/c7bfea2e903e4e23e09f290c298f61fa71e49882/build.gradle.kts#L295-L334 The dependencies are taken from Gradle dependencies which look like https://github.com/vlsi/calcite-avatica/blob/c7bfea2e903e4e23e09f290c298f61fa71e49882/core/build.gradle.kts#L27-L39 Here's an example how "shaded" dependencies are declared: https://github.com/vlsi/calcite-avatica/blob/c7bfea2e903e4e23e09f290c298f61fa71e49882/tck/build.gradle.kts#L39-L49 Note how it is immediately visible which ones are shaded and which are not. Vladimir
