kotlin-dsl-gradle-jooq-plugin
kotlin-dsl-gradle-jooq-plugin copied to clipboard
rohanprabhu
Handle classpath disparity between plugin target and runtime target
Since the plugin uses references to certain jooq objects that it is built with, there might be scenarios where the objects that are being referenced for configuration computation do not align with the references when the plugin is actually run. This causes issues, one of which is documented here : https://github.com/rohanprabhu/kotlin-dsl-gradle-jooq-plugin/issues/19
The original author of this issue has proposed a solution, which works for the time being, but I am keeping this issue opened here to further mull on the issue and evaluare if Reflections is the best way to solve it.
I don't know if we can do something else, so I'm very interested about a better solution!
What would be good is to be able to fetch the version of jooq used by the project instead of defining it in the plugin.
Very useful when used with Spring Boot, Micronaut (and Quarkus soon) when version are managed outside of the standard project.
What would be good is to be able to fetch the version of jooq used by the project instead of defining it in the plugin.
Very useful when used with Spring Boot, Micronaut (and Quarkus soon) when version are managed outside of the standard project.
This is very interesting, and would help to work better with the Gradle constraints for dependency version.
