Use new Gradle dependency configurations while generating the correct Maven pom

[Emanuel Rabina]

In #208, I learned that using Gradle's implementation dependency configuration, meant as the replacement for compile (which is now deprecated), generates the wrong kind of POM file needed for Maven, preventing a project that depends on the layout dialect to fail to compile.

Compare:

• 2.4.1 (working): https://search.maven.org/remotecontent?filepath=nz/net/ultraq/thymeleaf/thymeleaf-layout-dialect/2.4.1/thymeleaf-layout-dialect-2.4.1.pom
• 2.5.0 (broken): https://search.maven.org/remotecontent?filepath=nz/net/ultraq/thymeleaf/thymeleaf-layout-dialect/2.5.0/thymeleaf-layout-dialect-2.5.0.pom

There must be a way to be able to use the new configuration while generating the right kind of POM. In my brief look at the subject while fixing #208, the api configuration from the java-library plugin might be the way to go? See:

• https://docs.gradle.org/current/userguide/dependency_management_for_java_projects.html#sec:configurations_java_tutorial
• https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_configurations_graph

[Emanuel Rabina]

Yup, that seems to do it. Fixed in 6b51020