Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Introduce new metadata marker for Gradle 6 (#11109)

See: https://github.com/gradle/gradle/issues/11105

  1. … 14 more files in changeset.
Introduce new metadata marker for Gradle 6

See: https://github.com/gradle/gradle/issues/11105

  1. … 14 more files in changeset.
Introduce new metadata marker for Gradle 6

See: https://github.com/gradle/gradle/issues/11105

  1. … 14 more files in changeset.
Introduce new metadata marker for Gradle 6

See: https://github.com/gradle/gradle/issues/11105

  1. … 11 more files in changeset.
Support POM exclusions with implicit wildcard

A POM exclusion can specify only the groupId or the artifactId, implying

that the other one is set as "*".

Bump metadata cache version as we now parse more excludes than before.

Fixes #5092

  1. … 4 more files in changeset.
Revert: Add scope to maven dependency key (#4244)

Revert: Add scope to maven dependency key

Reverts a82cf4a but increases the cache layout version, as this

is now a new combination of changes.

It fixes #4202 and adds a test for 'duplicated dependency management entries override behavior' which covers the reported issue.

  1. … 9 more files in changeset.
Add scope to maven dependency key

Different versions could be defined for compile/runtime scope in

the dependency management block.

This is for example how Gradle publishes dependency constraints

to <dependencyManagement> for the same dependency with different

versions in a Java Library:

<dependencyManagement>

<dependencies>

<dependency>

<groupId>org.test</groupId>

<artifactId>bar</artifactId>

<version>1.0</version>

<scope>compile</scope>

</dependency>

<dependency>

<groupId>org.test</groupId>

<artifactId>bar</artifactId>

<version>1.1</version>

<scope>runtime</scope>

</dependency>

</dependencies>

</dependencyManagement>

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

  1. … 8 more files in changeset.
Some simplifications to the Ivy and Maven metadata parsing. Don't extract and persist the `description` and `publicationDate` properties for Ivy and Maven as these values are not required for dependency resolution. Incremented the cache version to reflect this change.

Removed some dead code that attempted to include a `description` in a generated ivy.xml, as there is no way to specify this in the Gradle DSL.

Moved some Maven metadata properties from constructor parameters to mutable properties.

  1. … 17 more files in changeset.
Refactor pom property handling for readability

  1. … 2 more files in changeset.
Use the module identifier factory in maven parsing too

  1. … 28 more files in changeset.
Corral Ivy usages to a smaller set of packages

  1. … 25 more files in changeset.
Revert experimental module descriptor parser changes

- Revert "Don't validate Ivy module descriptor files by default"

- This reverts commit 0a44ed73750a3e29d204c6fad7bfea8e5a0ad24f.

- Revert "Move XML parser creation to core"

- This reverts commit fb340a2dee09cb2675cf74ff158f9129152d3a0c.

- Revert "Optimize maven metadata parsing"

- This reverts commit ce94c68e375f7b643b77e0eb1eca1f5b6d1b3d3f.

- Revert "Replace m2-entities injection hack in POM parser"

- This reverts commit 4985b82b9b7b59f2b4cc997d68f84995b2260fe4.

  1. … 12 more files in changeset.
Replace m2-entities injection hack in POM parser

- the original solution is Ivy legacy which supports HTML4 entities

in POM files. That solution is a bottleneck in pom file

parsing.

- Maven accepts illegal XML for its pom's

- https://issues.apache.org/jira/browse/IVY-921

- the replacement keeps the feature, but implements it in an efficient

way by using the STAX API.

- Woodstox 5 STAX parser is used directly

- Sufficient STAX support is missing in IBM JDK.

- IBM StAX parser doesn't support disabling

IS_REPLACING_ENTITY_REFERENCES property

- Woodstox is fastest XML parser available for Java 6.

- StaxMate StAX-to-DOM conversion is used

- conversion is fastest possible

- TrAX API StAX-to-DOM conversion is error prone since

the TranformationFactory implementation on the

classpath might not accept StAXSource as input.

  1. … 8 more files in changeset.
Revert "Replace m2-entities injection hack in POM parser"

This reverts commit 121396224deb463490c3ff6d78f03eb6968e505e.

  1. … 6 more files in changeset.
Replace m2-entities injection hack in POM parser

- the original solution is Ivy legacy which supports HTML4 entities

in POM files. That solution is a bottleneck in pom file

parsing.

- Maven accepts illegal XML for its pom's

- https://issues.apache.org/jira/browse/IVY-921

- the replacement keeps the feature, but implements it in an efficient

way by using the STAX API.

- Woodstox 5 STAX parser is used directly

- Sufficient STAX support is missing in IBM JDK.

- IBM StAX parser doesn't support disabling

IS_REPLACING_ENTITY_REFERENCES property

- Woodstox is fastest XML parser available for Java 6.

- StaxMate StAX-to-DOM conversion is used

- conversion is fastest possible

- TrAX API StAX-to-DOM conversion is error prone since

the TranformationFactory implementation on the

classpath might not accept StAXSource as input.

  1. … 6 more files in changeset.
Minor renames and reordering

+review REVIEW-5520

  1. … 2 more files in changeset.
GRADLE-3299 Handle references to ${parent.artifactId} in pom files - prior to this fix only ${parent.version} and ${parent.groupId} could be referenced

  1. … 1 more file in changeset.
Renamed subprojects/core-impl to subprojects/dependency-management.

    • -0
    • +851
    ./PomReaderTest.groovy
  1. … 1384 more files in changeset.