@advancedwebdeveloper Although I am curious to see if this builds, the direction of our Go projects/tools that use Gradle and the gogradle plugin is one where we integrate a newer/supported plugin for Go that does not assume (old/deprecated) go vendor or one where we seek to eliminate gradle or a need for a plugin altogether (as the "go" tools have matured and become quite simple as to not require plugins perhaps at all). Unless there is some compelling reason to update (e.g., a CVE) I would choose not to do so as what we have now is quite functional and a version 2 other tools use.
@advancedwebdeveloper Although I am curious to see if this builds, the direction of our Go projects/tools that use Gradle and the gogradle plugin is one where we integrate a newer/supported plugin for Go that does not assume (old/deprecated) go vendor or one where we seek to eliminate gradle or a need for a plugin altogether (as the "go" tools have matured and become quite simple as to not require plugins perhaps at all). Unless there is some compelling reason to update (e.g., a CVE) I would choose not to do so as what we have now is quite functional and a version 2 other tools use.