Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge pull request #9009 from gla3dr/fix-typo-in-repositories-docs

Fix spelling of 'snaphshots'

Fix spelling of 'snaphshots'

Signed-off-by: gla3dr <zackmayoh@shaw.ca>

Fix spelling of 'snaphshots'

Signed-off-by: gla3dr <zackmayoh@shaw.ca>

Use visitor when snapshotting FileCollections

In many places when resolving and walking nested file collections we collect files into Sets. This is expensive because we have to de-duplicate the files. In many cases de-duplication doesn't need to happen, or it can happen only on the top level. In these cases visiting instead of collecting is a much better alternative.

This commit is a first step towards using more visitors. It introduces FileCollectionInternal.visitContents(Consumer<File>) and uses it in file snapshotting.

Use visitor when snapshotting FileCollections

In many places when resolving and walking nested file collections we collect files into Sets. This is expensive because we have to de-duplicate the files. In many cases de-duplication doesn't need to happen, or it can happen only on the top level. In these cases visiting instead of collecting is a much better alternative.

This commit is a first step towards using more visitors. It introduces FileCollectionInternal.visitContents(Consumer<File>) and uses it in file snapshotting.

Use visitor when snapshotting FileCollections

In many places when resolving and walking nested file collections we collect files into Sets. This is expensive because we have to de-duplicate the files. In many cases de-duplication doesn't need to happen, or it can happen only on the top level. In these cases visiting instead of collecting is a much better alternative.

This commit is a first step towards using more visitors. It introduces FileCollectionInternal.visitContents(Consumer<File>) and uses it in file snapshotting.

Fix binary compatibility

Since annotations on annotation methods have not yet been detected.

Fix binary compatibility

Since annotations on annotation methods have not yet been detected.

Merge pull request #9004 from gradle/revert-8991-lptr/core/use-guava-java-8

Revert "Use Java 8-compatible variant of Guava"

Revert "Use Java 8-compatible variant of Guava"

  1. … 11 more files in changeset.
Show from/to attributes on register failure

Locking now detects invalid force / substitute

Before this commit, a force or substitution was not detected by

dependency locking and would allow a user to have a graph result that

differed from the lock state.

With this commit, such differences are now properly reported and will

fail resolution when identified.

Closes #8971

Locking now detects invalid force / substitute

Before this commit, a force or substitution was not detected by

dependency locking and would allow a user to have a graph result that

differed from the lock state.

With this commit, such differences are now properly reported and will

fail resolution when identified.

Closes #8971

Locking now detects invalid force / substitute

Before this commit, a force or substitution was not detected by

dependency locking and would allow a user to have a graph result that

differed from the lock state.

With this commit, such differences are now properly reported and will

fail resolution when identified.

Closes #8971

Locking now detects invalid force / substitute

Before this commit, a force or substitution was not detected by

dependency locking and would allow a user to have a graph result that

differed from the lock state.

With this commit, such differences are now properly reported and will

fail resolution when identified.

Closes #8971

Detect wrong provider type at class generation time

Fix Guava performance regression

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

Fix Guava performance regression

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

Fix Guava performance regression

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

Fix Guava performance regression

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

See https://github.com/google/guava/issues/3223 for more details.

Address some review comments

WIP

Revert "Merge pull request #8991 from gradle/lptr/core/use-guava-java-8"

This reverts commit b3c791db65d344ddbe1878b56db41761db385aa5, reversing

changes made to 29c75bff79d89cfd6f69335a6bd056f1bdf1d160.

  1. … 11 more files in changeset.
add message

Update released version to latest snapshot

Update library versions in build init to latest for 5.6

Update version to 5.6

Merge remote-tracking branch 'origin/master-test' into release-test

Fail configuration phase deliberately

Fail configuration phase deliberately