PLUGIN AUTHORS: Please use the latest plugin-publish plugin - others may result in a broken upload


(Tom Dunstan) #1

Hi all

Some plugin authors have been having some issues uploading plugins when using older versions of the plugin-publish plugin to publish their plugins. This is due to some bugs in the older versions of this plugin coupled with some S3-related infrastructure changes made in the portal. These bugs were fixed in 0.9.7 of the plugin-publish plugin, which was released in December 2016.

All plugin authors need to upgrade to the latest version. Older versions result in a plugin version that appears in the portal but has no artifacts. We are working on some improvements to detect this state and stop new plugin versions from being activated when it occurs, but the only fix is using a non-broken publishing plugin.

In the meantime, if you have published a new version of your plugin and it is missing artifacts, let us know and we will delete the broken version to allow you to re-publish it. Please accept our apologies for the inconvenience.


Weird fail on plugins.gradle.org (enunciate 2.10.0)
Delete gradle-download-task 3.3.0
Could not find gradle.plugin.com
(Tom Dunstan) #2

(Boxfuse) #3

This upgrade breaks the withDependencies configuration.

We previously (with 0.9.1) had

withDependencies { dependencies ->
dependencies.add(new org.apache.maven.model.Dependency(groupId: ‘org.slf4j’, artifactId: ‘jcl-over-slf4j’, version: ‘1.7.12’))
dependencies.add(new org.apache.maven.model.Dependency(groupId: ‘org.slf4j’, artifactId: ‘slf4j-api’, version: ‘1.7.12’))
}

Yet with 0.9.7 this now breaks with

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

build file ‘/vagrant/client/build.gradle’: 56: unable to resolve class org.apache.maven.model.Dependency
@ line 56, column 22.
dependencies.add(new org.apache.maven.model.Dependency(groupId: ‘org.slf4j’, artifactId: ‘jcl-over-slf4j’, version: ‘1.7.12’))

We can’t find any examples for this at https://plugins.gradle.org/docs/publish-plugin

How can we fix this?


(Tom Dunstan) #4

Hi @boxfuse!

There’s something odd going on with the classpath here, as I can create a scratch project and paste your withDependencies block above in and it can resolve that class just fine.

Is the source for this gradle file somewhere public for me to have a look? If not, could you post either the whole file or all of your buildscript and plugins blocks? Also, which version of Gradle are you using?

Thanks

Tom


(Tim Yates) #5

Hi @boxfuse

I’m going to assume this is handled, and close this question for now. Please reach out in a new post if you’re still having issues?

Thanks!

Tim


(Tim Yates) #6