Gradle plugin v1.5.0 seems to be broken about gradle-scalafmt HOT 4 CLOSED

Hiya, Tim here from Gradle.

There was a bug in versions prior to 0.9.7 of the plugin-publish-plugin, where artifacts would silently not be pushed into the repo.

This unfortunately has affected v1.5.0 of the gradle-scalafmt plugin.

I see you have updated the plugin to a newer version, so it should just be a case of pushing a new version (1.5.1?) to the plugin portal

Once this is done, I can removed the broken 1.5.0 version if you'd like?

Thanks (and sorry about that).

Let us know here or in the forums if you need more assistance.

from gradle-scalafmt.

To test this, I added the plugin to one of my projects and the build seems to be passing alenkacz/postgres-scala@d7351c6

Are you resolving against jcenter? Can you share some error message or whole build.gradle so that I can help?

Thanks

from gradle-scalafmt.

Sure thing, sorry for taking so long.

The usual plugin applying way as lined out in your readme works like a charm. I was looking into gradle's short-notation way of doing it and referred to:

https://plugins.gradle.org/plugin/cz.alenkacz.gradle.scalafmt

Where the newest version doesn't seem to be pushed to per:

> Could not resolve all files for configuration ':common:scala:classpath'.
   > Could not find gradle.plugin.cz.alenkacz:gradle-scalafmt:1.5.0.
     Searched in the following locations:
         https://plugins.gradle.org/m2/gradle/plugin/cz/alenkacz/gradle-scalafmt/1.5.0/gradle-scalafmt-1.5.0.pom
         https://plugins.gradle.org/m2/gradle/plugin/cz/alenkacz/gradle-scalafmt/1.5.0/gradle-scalafmt-1.5.0.jar

I assume it's just a matter of publishing the artifacts to the correct server?

from gradle-scalafmt.

oh @timyates thank you! Just released 1.5.1 - feel free to remove 1.5.0

from gradle-scalafmt.