MavenPublishVersionRangeIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -2
    • +2
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 872 more files in changeset.
Merge branch 'master' into eskatos/ie/instantIntegTest-enable

    • -38
    • +0
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 8 more files in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

    • -36
    • +0
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 5 more files in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

    • -36
    • +0
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 5 more files in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

    • -36
    • +0
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 2 more files in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

    • -36
    • +0
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 2 more files in changeset.
Annotate integ tests failing with instant execution in :maven

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +3
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 39 more files in changeset.
Annotate integ tests failing with instant execution in :maven

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +3
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 39 more files in changeset.
Let maven-publish tests not use deprecated configurations

    • -9
    • +9
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 8 more files in changeset.
Let maven-publish tests not use deprecated configurations

    • -9
    • +9
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 8 more files in changeset.
Let maven-publish tests not use deprecated configurations

    • -9
    • +9
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 8 more files in changeset.
Polish some maven-publish tests

    • -1
    • +1
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 4 more files in changeset.
Enable Gradle metadata publishing for all maven-publish tests

- Several tests are still failing

- Most of these seem related to the fact that we don't respect the modified publication coordinates

- Some required verifications are missing

- Dependency excludes are not yet supported, so we do not verify these for module metadata

    • -5
    • +10
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 19 more files in changeset.
Fix Java component publishing

When we introduced the `java-library` plugin, we made sure

the published POM reflects what a downstream project in the

same build would see: `api` dependencies are exposed, `implementation`

dependencies are hidden. The legacy `compile`/`runtime` dependencies

are exposed as well for backwards compatibility.

We forgot to adjust the tests for the existing `java` plugin,

leading to a confusing difference in behavior. The `java` plugin

was still hiding the legacy `compile` and `runtime` dependencies from

consumers. This was due to a bug in the implementation of `JavaLibrary`,

which was looking for the `api` configuration instead of the `apiElements`

configuration.

    • -4
    • +4
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 24 more files in changeset.
Renamed a bunch of publishing integration tests for consistency

    • -0
    • +105
    ./MavenPublishVersionRangeIntegTest.groovy
  1. … 15 more files in changeset.