We should be using our own gradle plugins to help build the plugin itself. There a number of ways this can be done.
This task requires research to determine:
[ ] optimal approach
That ensures the following:
[ ] plugins are built with up-to-date plugins
[ ] does not interfere with local maven builds (snapshots or releases)
[ ] does not require initial publication anywhere
[ ] no failing builds due to chicken/egg scenario
[ ] no manual fiddling such as commenting out a buildscript.dependencies.classpath declaration && then enabling it
[ ] future-proo - ideally uses includeBuild in settings.gradle.kts to leverage composite builds, since buildSrc will eventually be replaced by this technique.
We should be using our own gradle plugins to help build the plugin itself. There a number of ways this can be done.
This task requires research to determine:
That ensures the following:
buildscript.dependencies.classpathdeclaration && then enabling itincludeBuildinsettings.gradle.ktsto leverage composite builds, sincebuildSrcwill eventually be replaced by this technique.