Ok, so I committed Maven -> Gradle change. Even though I expect it to be ok, there might be glitches here and there. It would be great if someone could verify if the generated pom.xml files are good.
Note: Avatica pom.xml files are generated at build time, so they will be different from those that existed in Git. As a reminder, if you find yourself lost, try executing " ./gradlew tasks " (if you forget tasks, try ./gradlew) It should print relevant tasks, and I suggest we keep the most important tasks there, and we hide less important ones. The poms can be tested as follows: "manual inspection": $ ./gradlew generatePom && find . -name 'pom-default.xml' ./metrics/build/publications/metrics/pom-default.xml ./core/build/publications/core/pom-default.xml ./shaded/core/build/publications/avatica/pom-default.xml ./noop-driver/build/publications/noop-driver/pom-default.xml ./server/build/publications/server/pom-default.xml ./tck/build/publications/tck/pom-default.xml ./build/publications/avatica-parent/pom-default.xml ./build/publications/pluginMaven/pom-default.xml ./standalone-server/build/publications/standalone-server/pom-default.xml ./metrics-dropwizardmetrics/build/publications/metrics-dropwizardmetrics/pom-default.xml "install to local Maven" $ ./gradlew publishToMavenLocal It will install Avatica artifacts to Maven local, so it could be tested with other Maven projects. Vladimir
