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.
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:
In #208, I learned that using Gradle's
implementation
dependency configuration, meant as the replacement forcompile
(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:
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 thejava-library
plugin might be the way to go? See: