Publishing existing plugin org.gretty: plugin org.gretty has been submitted for approval by Gradle engineers

Help/Discuss Plugin Portal
1

It’s been a while between releases to Gradle - Plugin: org.gretty … trying to beat the Bintray deadline before moving elsewhere … v3.0.3 is current on Plugins, when attempting to publish 3.0.4 using valid API Key I get:

Thank you. Your new plugin org.gretty has been submitted for approval by Gradle engineers. The request should be processed within the next few days, at which point you will be contacted via email.

Full output:

$ ./gradlew publishPlugins

> Task :libs:gretty:publishPlugins
Publishing plugin org.gretty version 3.0.4
Thank you. Your new plugin org.gretty has been submitted for approval by Gradle engineers. The request should be processed within the next few days, at which point you will be contacted via email.
Publishing artifact build/libs/gretty-3.0.4.jar
Publishing artifact build/libs/gretty-3.0.4-sources.jar
Publishing artifact build/libs/gretty-3.0.4-javadoc.jar
Publishing artifact build/libs/gretty-3.0.4-groovydoc.jar
Publishing artifact build/publications/pluginMaven/pom-default.xml
Activating plugin org.gretty version 3.0.4

BUILD SUCCESSFUL in 14s
15 actionable tasks: 2 executed, 13 up-to-date

Anything special I need to do here - are uploaders being revalidated, or are out build changes invalid?

Since the last release, java-gradle-plugin has been implemented, and I had to work-around issues such as discussed in Invalid plugin ID 'plugin-name': multiple plugins are using the same ID .

If someone could check the Gretty 3.0.4 for any weird differences from 3.0.3, and/or advise on any required approvals that would be appreciated.

1 Like
2

Hello,

I confirm that the plugin looks new from the Gradle Plugin Portal perspective.
This is because the new version uses org.gretty:gretty as the JAR coordinates instead of gradle.plugin.org.gretty:gretty previously. Note that this is a good change IMO.

The plan is to approve the plugin under these new coordinates.

The only impact for end users would be if they use the apply: form for getting the plugin. They would need to change the coordinates in the classpath declaration.

If you do not want that change in a minor, you should amend the publication and publish a 3.0.5.

3

Hi there, same for me and the update to 1.5.1 of com.kiwigrid.helm plugin. We did not intentionally change anything I can imagine would make the plugin appear new to your systems (here is the diff). We did however update gradle from 6.0.1 to 6.8.3. Here is the build output:

> Task :publishPlugins
Publishing plugin com.kiwigrid.helm version 1.5.1
Thank you. Your new plugin com.kiwigrid.helm has been submitted for approval by Gradle engineers. The request should be processed within the next few days, at which point you will be contacted via email.
Publishing artifact build/libs/gradle-helm-plugin-1.5.1.jar
Publishing artifact build/libs/gradle-helm-plugin-1.5.1-sources.jar
Publishing artifact build/libs/gradle-helm-plugin-1.5.1-javadoc.jar
Publishing artifact build/libs/gradle-helm-plugin-1.5.1-groovydoc.jar
Publishing artifact build/publications/pluginMaven/pom-default.xml
Activating plugin com.kiwigrid.helm version 1.5.1

BUILD SUCCESSFUL in 1m 35s
14 actionable tasks: 14 executed

Any suggestions or ideas?

1 Like
4

FYI: The plugin submission has been approved with the note that “the group has been approved”. Probably the policies changed since the last time we submitted a version…