MavenPublishCustomComponentIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

    • -8
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 2 more files in changeset.
Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

    • -8
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 2 more files in changeset.
Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

    • -8
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 2 more files in changeset.
Add validation at publication time

This commit introduces validation when generating Gradle

Module Metadata:

- check that there's at least one variant published

- each variant must have at least one attribute

- there shouldn't be duplicate variant names

- each variant must have a different (attributes,capabilities)

combination

Closes #10736

    • -6
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 11 more files in changeset.
Add validation at publication time

This commit introduces validation when generating Gradle

Module Metadata:

- check that there's at least one variant published

- each variant must have at least one attribute

- there shouldn't be duplicate variant names

- each variant must have a different (attributes,capabilities)

combination

Closes #10736

    • -6
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 11 more files in changeset.
Add validation at publication time

This commit introduces validation when generating Gradle

Module Metadata:

- check that there's at least one variant published

- each variant must have at least one attribute

- there shouldn't be duplicate variant names

- each variant must have a different (attributes,capabilities)

combination

Closes #10736

    • -6
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 11 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -28
    • +0
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 43 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -28
    • +0
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -28
    • +0
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -28
    • +0
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 29 more files in changeset.
Publish configuration-wide excludes in Ivy metadata

Resolves #4356.

    • -0
    • +1
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 17 more files in changeset.
Rename `CapabilitiesDescriptor` to `Capabilities`

... and `getCapababilitiesMetadata()` to `getCapabilities()` for consistency.

    • -1
    • +1
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 36 more files in changeset.
Publish capabilities to Ivy/Maven repositories

This commit makes sure that capabilities can be published to Maven or Ivy repositories.

By published, we only mean using Gradle metadata: capabilities are a Gradle-only feature,

so there's no equivalent to be published in a `pom.xml` or `ivy.xml` file.

    • -0
    • +1
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 15 more files in changeset.
Transform FeaturePreviewsFixture to use the new API

Replaces injecting a property in the gradle.properties with injecting

the gradle.enableFeaturePreview in settings.gradle

    • -1
    • +1
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 16 more files in changeset.
Turn experimental option into gradle metadata option

Signed-off-by: Jendrik Johannes <jendrik@gradle.com>

    • -1
    • +1
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 18 more files in changeset.
Rename 'experimental features' to 'feature previews'

The idea behind this is that we have a set of feature previews rather

than one cryptic experimental flag.

A feature preview collects a set of related functionality (e.g.

everything related to gradle metadata) that changes existing behavior

and thus could potentially break existing builds. The preview options

will be removed with the next major release (currently 5.0) and the new

behaviour will then become the default.

Signed-off-by: Jendrik Johannes <jendrik@gradle.com>

    • -2
    • +2
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 45 more files in changeset.
Adjust tests and test fixtures to opt-in options split

Signed-off-by: Jendrik Johannes <jendrik@gradle.com>

    • -1
    • +1
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 13 more files in changeset.
Adjust tests to use the new experimental feature option

Signed-off-by: Jendrik Johannes <jendrik@gradle.com>

    • -5
    • +4
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 23 more files in changeset.
Publish dependency constraints to Gradle module metadata

    • -0
    • +1
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 12 more files in changeset.
Use a fixture to enable experimental features in integTests

    • -3
    • +2
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 10 more files in changeset.
Simplify control of experimental features

- Removed ability to selectively enable features via DSL

- Renamed `enableAll()` -> `enable()`

- Can still selectively enable features via System property

    • -1
    • +1
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 11 more files in changeset.
Centralize management of experimental feature flags

Experimental features can be enabled via a system property,

or per-build-execution via the DSL available on the GradleInternal instance.

So far, only `publishModuleMetadata` is linked to this new flag.

    • -0
    • +30
    ./MavenPublishCustomComponentIntegTest.groovy
  1. … 9 more files in changeset.
Add test coverage for maven-publish with custom SoftwareComponent types

This test demonstrates how a custom SoftwareComponent can be published

using the `maven-publish` plugin, and verifies the produced module metadata.

Although we don't support custom implementations of SoftwareComponent at

this stage (implementing internal interfaces is required), this test already

provides some useful documentation of this mechanism.

    • -0
    • +149
    ./MavenPublishCustomComponentIntegTest.groovy