How are you affected by this?

It's probably a somewhat odd situation, but I using Maven to develop a Gradle plugin.

We're migrating our end-user tooling to be a plugin (and front-end if necessary) for Gradle rather than an ad-hoc collection of our own stuff, but the project itself is built with Maven and we don't particularly want to rewrite its build system right now. So I am trying to use Maven to fetch the necessary dependencies to write a Gradle plugin, and the absence of gradle-base-services-groovy means that Maven cannot compile my Gradle plugin.

I have worked around this issue by putting a repackaged Gradle JAR in my local Maven repository, but this issue may affect [publishing to Central]([1]http://forums.gradle.org/gradle/topic...).
----------------------------------------------------------------------------------------
[1] http://forums.gradle.org/gradle/topics/publish_source_and_javadoc_jars_for_gradle_to_maven_central

The current expectation is that Gradle plugins are built with Gradle, and that their POMs don't declare any Gradle dependencies. (Gradle is effectively a `provided` dependency). As far as I understand, the goal is to publish the wrapper and tooling API to repo.gradle.org, not necessarily the plugin API.

Nevertheless, thanks for the pointer that `gradle-base-services-groovy` isn't published to repo.gradle.org. This may be an oversight, and I'll take it back to the team.

That is an understandable expectation — trying to build a plugin for a build system with a different build system is, admittedly, a somewhat strange goal.

I am also affected by this. And no, building Gradle plugins with Maven is not uncommon. Any project with support for multiple tool plugins will at some point face this dilemma: stay with a single build tool or fork, run a second one, and reattach the artifacts. For me the first option is definitely the easiest.

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

This is now tracked by https://github.com/gradle/gradle/issues/1164.