Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge pull request #5074 from gradle/oehme/performance/gradleApi

Make gradleApi() method more efficient

Rename dist-snapshots repo to kotlin-dsl-snapshots-local

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
  1. … 32 more files in changeset.
Add ability to use `RegularFile` and `Directory` as publishable artifacts

Allows the use of `Directory` and `RegularFile` artifacts from projects.

`Provider<Directory>` and `Provider<RegularFile>` are already supported, so this make the "non-calculated" case supported as well.

Signed-off-by: Mike Kobit <mkobit@gmail.com>

Make a bunch of shit lazy

    • -5
    • +5
    /subprojects/integ-test/integ-test.gradle
Merge pull request #819 from gradle/bamboo/samples/buildSrc-plugin

Add `buildSrc-plugin` sample

Make TAPI performance tests profilable

Rebaseline Android Studio performance test

The last baseline didn't include all of the changes

that led to the slight regression, so the test was still

failing.

Evaluate signature file location lazily

The artifact to sign could still change and the signature

depends on its path. Evaluate it lazily so artifacts can be

configured until the task graph is built.

Add descriptions to Sign tasks for configurations/publications/tasks

Resolves #5093.

Query published artifact coordiantes lazily

This is another step towards removing DeferredConfigurable.

Instead of eagerly evaluating archive tasks and other artifacts,

query their properties only when we actually want to publish.

Make derived artifacts optional when publishing

Fixes #5099.

Make MavenPublication.from(SoftwareComponent) lazy

This prevents the software component from being read too early,

e.g. when configuring signing.

Previously any access of a publication resulted in the component

being read and any further modifications to it being ignored.

This is also a prerequisity for removing DeferredConfigurable.

Make MavenProjectIdentity live

This way the coordinates are only evaluated when needed.

Previously they were evaluated when a publicaiton was created.

Lots of users had worked around it by re-setting the values

to what should already be the defaults later.

Improve wording in IDEA Plugin chapter

Merge pull request #5071 from gradle/oehme/performance/cached-resource-lookups

Cache resources in caching classloader

Merge pull request #5072 from gradle/oehme/performance/external-module-lookup

Cache external module lookups

Merge pull request #5083 from gradle/oehme/performance/faster-mirror

Make mirror init script faster

Update wrappers to latest snapshot distro

Add test for sample

Merge pull request #826 from gradle/bamboo/integ-tests

Make generated precompiled script plugin code follow the kotlin-dsl coding conventions

Mark offending test with `@LeaksFileHandles`

Merge pull request #825 from gradle/eskatos/idea/gradle-idea-ext-plugin

Use idea-ext plugin experiment

Use umodifiable list in DefaultClassPath

This makes accidental mutation impossible and reduces some

of the repeated wrapping.

  1. … 23 more files in changeset.
Update Gradle perf baseline to commit that does not use snapshot build scan plugin

    • -1
    • +1
    /subprojects/performance/templates.gradle
Replace locking with concurrent map

DependencyClassPathNotationConverter didn't need pessimistic locking

as the protected operation is not expensive. Use a concurrent map instead.

Use idea-ext plugin

- license header

- disable unwanted frameworks detection

Remove ext-releases-local repo as its included in the libs-releases repo

Defer gradleApi classpath lookup to execution time

It is only needed when the gradleApi file collection is constructed.

Restore correct locking in DependencyClassPathNotationConverter

This was broken when making the creation lazy, protecting the

creation method (which needs no lock) instead of the cache access

(which does need a lock).

Explain that IDEA import honors IDEA configuration

Clarify that IDEA's import facility doesn't require the build script to apply

the IDEA Plugin, but it will honor some forms of IDEA configuration if it does.