We have an internal plugin JAR that I’m starting to upgrade to M5. The build for the plugin JAR uses an version of itself, which happens to have some incompatibilities with M5. It fails while applying plugins, so I’m not able to build a new version of the JAR, as currently configured.
How should I handle this? It seems like the issue is that the gradleApi() method makes a tie between the version of gradle running your build and the version of gradle you are developing for. Assuming there’s not something else I’m missing, the best approach would be to decouple those.
Is there any way to decouple them right now, or am I stuck with some method of pulling the M5 JARs from the filesystem, while continuing to run the build itseld with M4?