BuildProgressCrossVersionSpec.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Ignore broken tooling API test.

    • -0
    • +2
    ./BuildProgressCrossVersionSpec.groovy
Fix TAPI test for Maven upload events

    • -4
    • +6
    ./BuildProgressCrossVersionSpec.groovy
Fix TAPI test for Maven upload events

    • -4
    • +6
    ./BuildProgressCrossVersionSpec.groovy
Fix TAPI test for Maven upload events

    • -4
    • +6
    ./BuildProgressCrossVersionSpec.groovy
Fix TAPI test for Maven upload events

    • -4
    • +6
    ./BuildProgressCrossVersionSpec.groovy
Adjust tests and samples to new publishing default behavior

    • -0
    • +3
    ./BuildProgressCrossVersionSpec.groovy
  1. … 43 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -0
    • +3
    ./BuildProgressCrossVersionSpec.groovy
  1. … 16 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -0
    • +3
    ./BuildProgressCrossVersionSpec.groovy
  1. … 16 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -0
    • +3
    ./BuildProgressCrossVersionSpec.groovy
  1. … 16 more files in changeset.
Bump version to 6.0

    • -1
    • +1
    ./BuildProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Bump version to 6.0

    • -1
    • +1
    ./BuildProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Bump version to 6.0

    • -1
    • +1
    ./BuildProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Bump version to 6.0

    • -1
    • +1
    ./BuildProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Update cross-version test for changed download behaviour with `maven-publish`

    • -8
    • +18
    ./BuildProgressCrossVersionSpec.groovy
Update cross-version test for changed download behaviour with `maven-publish`

    • -8
    • +18
    ./BuildProgressCrossVersionSpec.groovy
Fix tests

    • -1
    • +2
    ./BuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Fix tests

    • -1
    • +2
    ./BuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Do not use Maven libraries for publishing with `maven-publish`

The use of aether and other Maven libraries was problematic:

- Static state forced us to prohibit concurrent publishing tasks

- It was difficult to control/understand the generated `maven-metadata.xml` files

- Multiple layers of indirection Gradle->Maven->Gradle->Maven made the code

difficult to comprehend and modify

Publishing of snapshot modules is not yet working. This will come in a

subsequent commit.

    • -1
    • +2
    ./BuildProgressCrossVersionSpec.groovy
  1. … 11 more files in changeset.
Do not use Maven libraries for publishing with `maven-publish`

The use of aether and other Maven libraries was problematic:

- Static state forced us to prohibit concurrent publishing tasks

- It was difficult to control/understand the generated `maven-metadata.xml` files

- Multiple layers of indirection Gradle->Maven->Gradle->Maven made the code

difficult to comprehend and modify

Publishing of snapshot modules is not yet working. This will come in a

subsequent commit.

    • -1
    • +2
    ./BuildProgressCrossVersionSpec.groovy
  1. … 11 more files in changeset.
Do not use Maven libraries for publishing with `maven-publish`

The use of aether and other Maven libraries was problematic:

- Static state forced us to prohibit concurrent publishing tasks

- It was difficult to control/understand the generated `maven-metadata.xml` files

- Multiple layers of indirection Gradle->Maven->Gradle->Maven made the code

difficult to comprehend and modify

Publishing of snapshot modules is not yet working. This will come in a

subsequent commit.

    • -1
    • +2
    ./BuildProgressCrossVersionSpec.groovy
  1. … 11 more files in changeset.
Do not use Maven libraries for publishing with `maven-publish`

The use of aether and other Maven libraries was problematic:

- Static state forced us to prohibit concurrent publishing tasks

- It was difficult to control/understand the generated `maven-metadata.xml` files

- Multiple layers of indirection Gradle->Maven->Gradle->Maven made the code

difficult to comprehend and modify

Publishing of snapshot modules is not yet working. This will come in a

subsequent commit.

    • -1
    • +2
    ./BuildProgressCrossVersionSpec.groovy
  1. … 11 more files in changeset.
Remove support for TAPI clients <3.0

    • -2
    • +0
    ./BuildProgressCrossVersionSpec.groovy
  1. … 63 more files in changeset.
Use setup/cleanup instead of rule

since the setup/cleanup method will be called by retry rule, while

the rule won't be re-instantiated again.

    • -3
    • +10
    ./BuildProgressCrossVersionSpec.groovy
Always init the TAPI provider with the shared user home

    • -2
    • +0
    ./BuildProgressCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Ignore failed test temporarily

    • -0
    • +2
    ./BuildProgressCrossVersionSpec.groovy
Don't log excessively and without task attribution when maven publishing (#4758)

There are two changes here:

1. Propagate the task build operation ref to the threads used by Aether to transfer to/from maven repositories so that we attribute the logging to the publish task.

2. When we fail to find metadata before uploading, log at info instead of error. This is not an error condition.

    • -0
    • +95
    ./BuildProgressCrossVersionSpec.groovy
  1. … 7 more files in changeset.