Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Convert `platform-jvm` build script to Kotlin

    • -0
    • +29
    /subprojects/platform-jvm/platform-jvm.gradle.kts
Use safe locking for artifact resolution too

Convert `platform-base` build script to Kotlin

    • -0
    • +30
    /subprojects/platform-base/platform-base.gradle.kts
Convert `persistent-cache` build script to Kotlin

Move safe locking into a reusable object

Polish build scripts

- Remove redudant `.configure` call

- Make expressions readable under 120 columns

- Remove obvious type declarations from expressions

- Favour property syntax over method invocation syntax

- Keep arguments at the same indentation level

- Improve use of spaces

    • -7
    • +14
    /subprojects/launcher/launcher.gradle.kts
Avoid null assertion by using non-null extra property type

Convert `osgi` build script to Kotlin

    • -0
    • +35
    /subprojects/osgi/osgi.gradle.kts
Convert `native` build script to Kotlin

    • -0
    • +90
    /subprojects/native/native.gradle.kts
Publish 5.0-20181003125523+0000

Polish Kotlin build scripts

- Keep arguments at the same indentation level

Inject default exclude patterns into DirectorySnapshotter

Do not depend on Ant's DirectoryScanner.

Revert perf test rebaseline to investigate

Use ThreadSafe annotation from javax.annotation

This is to avoid depending on other projects

Revert "Ignore broken tests"

This reverts commit db3f561a7424f9f4f1d2dc191c500f1592a7e41f.

Fixes gradle/gradle-private#1568

Merge pull request #6999 from gradle/fg/build-scan-plugin-2-0

Build scan plugin 2.0 simplifications

Add incubation reports tab

Add all individual reports to the incubation report zip

Cosmetics for incubating API tasks

Revert "Rebase `JavaFirstUsePerformanceTest` on latest nightly"

The rebase was done out of desperation to get the 5.0-milestone-1

released. It's most likely a bad rebase and we should investiguate if

it keep failing.

This reverts commit 7255bad6aab13455c50d1d21e56bce2c82bec40a.

Introduce an incubating APIs report

This commit adds an incubating APIs report to all Java projects. One

can get a report of the incubating APIs by running the `incubationReport`

task.

An aggregate task, bound to `sanityCheck`, is also available:

- `allIncubationReportsZip` will generate a report aggregating all projects incubating APIs

- `allIncubationReports` will do the same but without a zip. This tasks is not bound to `sanityCheck`.

Merge pull request #6993 from gradle/lacasseio/kotlin/build-script-conversion

Convert build scripts to Kotlin

Add daily trigger to `Release - Snapshot` job.

So we can automatically publish its related metadata into `services.gradle.org` to be consumed

by GE testing automation.

Fix link to task timeouts section

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
Fix link to task timeouts section

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
Reintroduce some limited synchronization for configuration resolution

This ensures that only one thread is resolving the graph of a given

configuration at a time.

When we step over to other projects while resolving configurations, we

will release the current project lock. This can allow other tasks to

start running. When they do, there can be issues when they try to

continue resolving the graph of the same configuration as the first

task. For example, a beforeResolve hook can cause the project lock

to be released (perhaps by resolving another configuration) and then

another task can put the configuration in an unexpected state before

the project lock can be reacquired..

Remove application plugin from misbehaving plugins

The application plugin now creates and references tasks lazily. As such,

the plugin can be removed from the list of misbehaving plugins in

WellBehavedPluginTest.

Signed-off-by: Kevin Macksamie <kevin.macksamie@gmail.com>

Use lazy task API in the application plugin

Signed-off-by: Kevin Macksamie <kevin.macksamie@gmail.com>

Exclude application plugin from behaved plugins

With the ApplicationPluginIntegrationTest inheriting the tests from

WellBehavedPluginTest, it fails the "does not realize all possible

tasks" test. In order to make the test pass, the application plugin must

be included in the list of misbehaving plugins inside that test. This

confirms that the application plugin in its current state is not lazy.

Signed-off-by: Kevin Macksamie <kevin.macksamie@gmail.com>

Re-enable compatibility check