Please publish plugin version 4.0.0 on plugins.gradle.org

[ieugen]

Hello,

I've noticed that version 4.0.0 is not available on the gradle plugins website [1] https://plugins.gradle.org/plugin/biz.aQute.bnd.builder .

Could you please publish it.

Thanks,

[rotty3000]

I just learned that we can publish a binary plugin (which is what we need) to the gradle plugin portal.

For reference take a look here [1] Flip over the the "full example" and look at the very bottom:

  // Optional overrides for Maven coordinates.
  // If you have an existing plugin deployed to Bintray and would like to keep
  // your existing group ID and artifact ID for continuity, you can specify
  // them here.
  //
  // As publishing to a custom group requires manual approval by the Gradle
  // team for security reasons, we recommend not overriding the group ID unless
  // you have an existing group ID that you wish to keep. If not overridden,
  // plugins will be published automatically without a manual approval process.
  //
  // You can also override the version of the deployed artifact here, though it
  // defaults to the project version, which would normally be sufficient.

  mavenCoordinates {
    groupId = "org.samples.override"
    artifactId = "greeting-plugins"
    version = "1.4"
  }

[1] https://plugins.gradle.org/docs/publish-plugin

[bjhargrave]

I don’t think that says what you think it says.

On Fri, Jun 8, 2018 at 15:18 Raymond Augé notifications@github.com wrote:

I just learned that we can publish a binary plugin (which is what we need) to the gradle plugin portal.

For reference take a look here [1] Flip over the the "full example" and look at the very bottom:

// Optional overrides for Maven coordinates. // If you have an existing plugin deployed to Bintray and would like to keep // your existing group ID and artifact ID for continuity, you can specify // them here. // // As publishing to a custom group requires manual approval by the Gradle // team for security reasons, we recommend not overriding the group ID unless // you have an existing group ID that you wish to keep. If not overridden, // plugins will be published automatically without a manual approval process. // // You can also override the version of the deployed artifact here, though it // defaults to the project version, which would normally be sufficient.

mavenCoordinates { groupId = "org.samples.override" artifactId = "greeting-plugins" version = "1.4" }

[1] https://plugins.gradle.org/docs/publish-plugin

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bndtools/bnd/issues/2468#issuecomment-395893006, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQ8spLeA9DaEsbTWvGqaVBduZspDCzsks5t6uoPgaJpZM4Ug8wx .

-- BJ

[soberich]

@ieugen This little pain is a dublicate. See @bjhargrave 's https://github.com/bndtools/bnd/issues/1850#issuecomment-394101274

@bjhargrave Maybe this could somehow help with the direction. https://github.com/iherasymenko/lombok-publisher Here this guy clones lombok and publishes it daily automatically. The logic could be different, not "daily" but, say, when version "x.x.0" released or simply manually, when you decide, as you said, "ok, this one we want release" go there and execute ./gradlew publish (which set non-default task) from the sources which were constantly cloned by travis from you github, The automation is quiet high and limited to just executing one command.

[ieugen]

Hello @soberich , thanks for the suggestion. I will definitely use that for a few projects. I asked here since I imagined the organization would like to be involved/manage this process. I also know that some restrictions apply when you wish to publish binary artifacts on Maven plugin portals - for security reasons, publishing is restricted to the domain/organization owner.

But if that is not the case here I might put up a publisher. However, as you said, having this high level of automation it makes sense to make official publications.

Regards,

[bjhargrave]

Maybe this could somehow help with the direction. https://github.com/iherasymenko/lombok-publisher Here this guy clones lombok and publishes it daily automatically.

That has nothing to do with the gradle plugin publishing to the Gradle plugin portal. That is just publishing an artifact to a maven snapshot repo which is quite straighforward.

[bjhargrave]

I have also published versions 3.4.0, 3.5.0, and 4.0.0 to the Gradle Plugin Portal.