MavenVersionRangeResolveIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Let dependency-management tests not use deprecated configurations

    • -5
    • +5
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -5
    • +5
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -5
    • +5
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -5
    • +5
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
Implement variant derivation strategy

This commit changes how Maven metadata is derived into variants. Now we will

only derive variants if the Java plugin is applied (the "base Java" plugin).

This is implemented via a variant derivation strategy, and allows fixing

the problem that a native component is unlikely to find sense in the derivation

of Java variants. This fixes a bug where the native plugins wouldn't be able

to consume native libraries published on Maven repositories, without Gradle

metadata.

    • -0
    • +4
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 43 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.

    • -0
    • +3
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 50 more files in changeset.
Collect unmatched dependencies too

Without this change, it is not possible to know which versions Gradle

considered for a dynamic range, unless it's rejected by a rule or by

attribute matching.

    • -1
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 19 more files in changeset.
Collect unmatched dependencies too

Without this change, it is not possible to know which versions Gradle

considered for a dynamic range, unless it's rejected by a rule or by

attribute matching.

    • -1
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 19 more files in changeset.
Change int tests to use relevant fixture methods to express their expectations about the build log output.

    • -1
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 28 more files in changeset.
Refine version range related classes and tests

    • -0
    • +78
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 5 more files in changeset.
Support parent POMs with version-range

https://github.com/gradle/gradle/issues/1898

As stated in https://maven.apache.org/docs/3.2.2/release-notes.html ,

Maven supports parent POM version with range. When Gradle resolves

parent POMs, it didn't take version range into consideration. This PR

adds some resolution for dynamic parent POM version.

    • -0
    • +39
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 1 more file in changeset.
Don't create an Ivy ModuleDescriptor when parsing POM files

    • -1
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 8 more files in changeset.
Moved `ResolveTestFixture` into a `org.gradle.integtests.fixtures` subpackage

This has the net effect of making this class visible to the Tooling API integration

tests, since the `org.gradle.integtests.fixtures` package is explicitly allowed

in the filtering classloader used by the TAPI integration tests.

    • -1
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 8 more files in changeset.
Fix integration test

    • -0
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
Add some test coverage for ivy repos, and switch to use ResolveTestFixture

+review REVIEW-5991

    • -7
    • +12
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
GRADLE-3334: Handle version ranges like [1.0] in a gradle dependency

    • -0
    • +55
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 3 more files in changeset.