Gradle

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
enhanced test source folder detection for eclipse task. (#10320)

Fixes eclipse/buildship#909

Signed-off-by: Christian Dietrich <christian.dietrich@itemis.de>

Publish 5.6.1-20190823130927+0000

Autodetect TestFramework if none is configure explicitly

When the TestFramework of a Test task is not configured explicitly it

used to default to `useJUnit()`. Now, the task's classpath is inspected

for a junit-platform-engine.jar or testng.jar. If one of them is found,

the task uses the JUnit Platform or TestNG to execute tests,

respectively.

Since we have internal dependencies on the JUnit Platform and TestNG,

all Test tasks in our own build are configured to `useJUnit()` and

explicitly.

Fix Jacoco broken by now correct enum deserialization

by removing usages of Project

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

Refine EnumCodec

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

Refine EnumCodec

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

Refine EnumCodec

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

Rebase performance tests with 5.7-20190812122716+0000 baseline

#10348 might have an influence on the performance of these scenarios.

Add some groovydoc to android-instant-execution fixture

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

Introduce instant execution enum codec

Previously, spurious instances of enums were created when loading from

the cache, leading to comparison failures, observed with AGP.

Not more covered android tasks because the very same task now fails

with another problem.

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

Turn 'multiple publications with same coordinates' error into warning

This reduces the severity of the error detection introduced in #9466.

Although this situation is technically an error that should be avoided

as it causes information loss in the published result, in some testing

scenarios builds may rely on this behavior. So instead of failing,

Gradle now prints a warning message.

Turn 'multiple publications with same coordinates' error into warning

This reduces the severity of the error detection introduced in #9466.

Although this situation is technically an error that should be avoided

as it causes information loss in the published result, in some testing

scenarios builds may rely on this behavior. So instead of failing,

Gradle now prints a warning message.

Simplify the bytecode generation for managed read only properties, so that fewer assumptions are baked into the generation.

Simplify the bytecode generation for managed read only properties, so that fewer assumptions are baked into the generation.

Simplify the bytecode generation for managed read only properties, so that fewer assumptions are baked into the generation.

Simplify the bytecode generation for managed read only properties, so that fewer assumptions are baked into the generation.

Simplify the bytecode generation for managed read only properties, so that fewer assumptions are baked into the generation.

Simplify the bytecode generation for managed read only properties, so that fewer assumptions are baked into the generation.

Fix for previous commits.

Fix for previous commits.

Fix for previous commits.

Fix for previous commits.

Upgrade wrapper to 6.0 nightly

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Merge branch 'release'

Rebase performance tests with 5.7-20190722220035+0000 baseline

#10348 might have an influence on the performance of these scenarios.

  1. … 11 more files in changeset.
Merge pull request #10339 from gradle/eskatos/ie/it-santa-tracker

Integration test Santa Tracker with Instant Execution

Fixes for lastest 2.0 snapshot

fixes for tests.

Adjust comparator

Override getResources in DefaultDeprecatedClassLoader

This fixes https://github.com/gradle/gradle/issues/10347

In https://github.com/gradle/gradle/pull/9898 we introduced a DefaultDeprecatedClassLoader,

which overrides getResource() but not getResources(). This causes some issues.

This PR fixes the issue by correctly overriding getResources() method.