Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Recompute selected component when removing selector

Previously, once a component was selected, removing a selector would not

change the resolution result, potentially keeping a selection that no

longer applied.

Now upon removal of a selector, the selected component may be updated.

In order to prevent infinite loops in some cases, the recompute on

removal only happens once per SelectorState instance.

Fixes #6567

Merge pull request #11566 from gradle/vvaluckas/disable-build-cache-per-stage

Add flag to disable build cache for a pipeline stage

Move stage arguments to a single line

    • -12
    • +1
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Add maxFailures property to PMD (resolves #11557)

Signed-off-by: Matthew Duggan <mgithub@guarana.org>

Refine :smokeTest build script

Signed-off-by: Paul Merlin <paul@gradle.com>

Refine :smokeTest build script

Signed-off-by: Paul Merlin <paul@gradle.com>

Refine :smokeTest build script

Signed-off-by: Paul Merlin <paul@gradle.com>

Refine :smokeTest build script

Signed-off-by: Paul Merlin <paul@gradle.com>

Clarify variable name

Remove weird file

Remove weird file

Only use the JDK watcher on Linux

So Windows uses a noop watcher now. This means we don't need to wait 2 seconds in our integration tests anymore.

Only use the JDK watcher on Linux

So Windows uses a noop watcher now. This means we don't need to wait 2 seconds in our integration tests anymore.

Only use the JDK watcher on Linux

So Windows uses a noop watcher now. This means we don't need to wait 2 seconds in our integration tests anymore.

Merge pull request #11567 from gradle/lacasseio/docs/typo-no-java-application-plugin

Mention `application` plugin

Mention `application` plugin

The `java-application` plugin doesn't exists.

Add flag to disable build cache for a pipeline stage

    • -2
    • +25
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Make Ktlint happy

Recognize Kotlin script caches as additive caches

And stop watching compiled Kotlin DSL directories.

Fix error message

Rename experimental pipeline to follow the convention