Cédric Champeau

Fix TAPI tests

Typo: signatures -> checksums

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
Typo: signatures -> checksums

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
Fix TAPI test for Maven upload events

Fix TAPI test for Maven upload events

Fix TAPI test for Maven upload events

Fix TAPI test for Maven upload events

Fix unit test

Fix unit test

Fix unit test

Fix unit test

Add tests to prove resiliency of SHA signature uploads

Add tests to prove resiliency of SHA signature uploads

Add tests to prove resiliency of SHA signature uploads

Add tests to prove resiliency of SHA signature uploads

Add tests to prove resiliency of SHA signature uploads

Fix signing test cases

Fix signing test cases

Fix signing test cases

Fix signing test cases

Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

    • -1
    • +4
    /subprojects/docs/src/docs/release/notes.md
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

    • -1
    • +4
    /subprojects/docs/src/docs/release/notes.md
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

    • -1
    • +4
    /subprojects/docs/src/docs/release/notes.md
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

    • -1
    • +4
    /subprojects/docs/src/docs/release/notes.md
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +5
    /subprojects/docs/src/docs/release/notes.md
  1. … 19 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +5
    /subprojects/docs/src/docs/release/notes.md
  1. … 19 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +5
    /subprojects/docs/src/docs/release/notes.md
  1. … 19 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +5
    /subprojects/docs/src/docs/release/notes.md
  1. … 19 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +5
    /subprojects/docs/src/docs/release/notes.md
  1. … 19 more files in changeset.
Add a `add-plugin` CLI option

This commit introduces a new CLI flag, `--add-plugin`, which allows adding a plugin to a build

directly from the command line. The main advantage of this is that there's no need to have a

build file to be able to download an apply a plugin.

There are different use cases for this, but mainly, this is about _bootstraping_ plugins.

For example, the vert.x team could publish a plugin which generates a templated Gradle build.

All the user would have to do would be something like:

`gradle --add-plugin com.vertx.bootstrap:1.5`

and then the plugin would take care of generating a build.

Another use case is to add diagnostics (build scans is an example of this but there's already

a built-in mechanism, --scan, to do this).

This spike is _compatible with included builds_, meaning that you can bootstrap with

a plugin currently in development using `--include-build`.