Multi-project publish ignores repo in one of the subprojects

[budjb]

I have a build with many libraries that are set up to publish to bintray. One of those subprojects is a Grails 3 plugin, which uses the bintray underneath Grails' own logic. The Grails project is special in that I deploy that artifact to a different repository (named grails-plugins) than the other libraries in the project (which go to maven).

The behavior I'm seeing is that all artifacts upload to bintray correctly, but I see a failure in the publish stage for the Grails plugin. Inspecting the URL for the publish step for the Grails plugin shows that it attempts to hit the URL for the artifact under the maven repository instead of the grails-plugins repository.

The only way to finish the publish is to log into bintray and click the publish link in the notification that I have unpublished artifacts.

You can see my setup at https://github.com/budjb/http-requests. Please let me know what else you might need to investigate this.

[eyalbe4]

Hi @budjb,
The plugin currently supports publishing to multiple versions and packages from different subprojects, but it does not yet support publishing to multiple repositories. We'll make sure to include this in the coming release.

[ollehallin]

Any estimated date for this new version?

I have this situation as well, one generic repo with dist zips and a Maven repo with a java agent jar.

[eyalbe4]

@ollehallin, we will try to have this functionality released before the end of next week.

[ollehallin]

It works fine now!

(BTW: README.md still references version 1.6)

Olle

[eyalbe4]

Great to hear @ollehallin!
I was just about to notify you we managed to release 1.7. I've just updated the README.
@budjb, you can try it our as well.
See the full release notes here