Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

    • -2
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
Fix Ivy tests after variant renaming

  1. … 3 more files in changeset.
Always evaluate publishing block eagerly

This commit makes `enableFeaturePreview('STABLE_PUBLISHING')`

meaningless by always using the new behavior. The flag is kept for

backward compatibility.

  1. … 55 more files in changeset.
Always evaluate publishing block eagerly

This commit makes `enableFeaturePreview('STABLE_PUBLISHING')`

meaningless by always using the new behavior. The flag is kept for

backward compatibility.

  1. … 55 more files in changeset.
Enable improved POM support by default

This commit makes the experimental flag `IMPROVED_POM_SUPPORT` the default.

The flag is still there for backwards compatibility but has effectively no

impact. As a consequence, the behavior of improved POM support is now the

default, which implies that:

- Maven dependencies packaged as `pom` or `jar` now have derived variants

(`compile` and `runtime`) and we properly choose between the variants based

on the consumer attributes

- platform dependencies using the `platform` and `enforcedPlatform` keywords

are enabled

Enabling improved POM support by default is a **breaking change**: there's

a risk that resolved dependencies is different, in particular because we

will now only include the `compile` dependencies of a POM file whenever the

consumer asks for the API variant. There are also some changes in the

dependency insight reports due to the use of attribute based matching instead

of configuration selection.

Last but not least, this commit is likely to introduce a small performance

regression due to attribute based selection.

  1. … 50 more files in changeset.
Nag users only once about stable_publishing flag

This was an oversight, it should have used the deprecation

logger, not a normal logger to print the warning.

  1. … 27 more files in changeset.
Nag users only once about stable_publishing flag

This was an oversight, it should have used the deprecation

logger, not a normal logger to print the warning.

  1. … 28 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. … 16 more files in changeset.
Turn experimental option into gradle metadata option

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

  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>

  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. … 13 more files in changeset.
Adjust tests to use the new experimental feature option

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

  1. … 23 more files in changeset.
Explicitly declare which tests require external dependencies

Ideally, those dependencies should be replaced with synthethic dependencies that mimic what they are doing.

In the meantime, the relatively low number of tests which do make use of external dependencies have been

marked as such. This should fix an error on CI, where the Artifactory mirror is not as quite tolerant as

what we allow in the component coordinates.

  1. … 4 more files in changeset.
Introduce `noComponentPublished()` expectation

This expectation needs to be used whenever we expect resolution failure because no component was published.

This happens with Gradle metadata only, as the only way to publish a module file is `from components....`

  1. … 14 more files in changeset.
Always resolve test publications with experimentFeatures enabled

Now that we can selectively choose which `metadataSource` to resolve

we can always verify the published metadata files with experimental

features enabled. This simplifies the tests.

One test needed to be changed because an optional dependency being

dragged in by spring-core was changing the resolution result when

experimental features were enabled.

  1. … 3 more files in changeset.
Migrate the Maven publish integration tests to use the same test fixtures as Ivy

This makes things much easier to understand, and explicits some expectations.

  1. … 12 more files in changeset.
Push common `sq` methods up to trait

  1. … 2 more files in changeset.
Enfore looking only for `ivy` or `gradle` metadata when doing resolution

This commit uses the `metadataSources` to make sure that when we re-resolve, we only use the expected metadata source.

This prevents some tests from accidentally passing because we resolve to Ivy after failing with Gradle.

  1. … 5 more files in changeset.
Resolve published Ivy files twice, with and without Gradle metadata

This commit changes the Ivy publication tests so that we resolve the published files twice:

- once with Gradle metadata

- once without Gradle metadata

Expectations are set on both, using a single entry point (`resolveArtifacts`). This removes the

explosion of `resolveArtifact` methods.

  1. … 12 more files in changeset.
Fix legacy Ivy publishing for null Exclude artifacts

    • -5
    • +5
    ./api/publish/ivy/AbstractIvyRemoteLegacyPublishIntegrationTest.groovy
  1. … 1 more file in changeset.
Make java libraries publishable on Ivy using Gradle metadata

This commit completes Gradle metadata publishing on Ivy repositories. It adds the necessary support, and

converts several tests to the wrapping `javaLibrary` test fixture.

  1. … 28 more files in changeset.
Use mavenCentral() and jcenter() mirrors in tests where possible

  1. … 51 more files in changeset.