Note, I'm not sure how we should handle this. Maven itself only populates this tag when publishing a plugin. Since I expect not many folks are publishing Maven plugins via Gradle I'm not sure if this is a useful feature. Additionally, we'd need to have some way for the build to indicate it is publishing a Maven plugin. Alternatively we could always populate this data but I'm not certain what kinds of side effects that might introduce for consumers.

https://github.com/apache/maven/blob/maven-3.3.9/maven-aether-provider/src/main/java/org/apache/maven/repository/internal/VersionsMetadata.java#L65-L68

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!

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.