Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix `gradlew` execution for non-standard systems

On older Solaris versions and other systems where `/bin/sh` is not

a POSIX-compliant shell, the shell syntax used by the wrapper

script fails on certain constructs.

Fix those cases where the wrapper script was doing some things not

supported on the older non-POSIX shells: using backticks instead

of `$()`, changing the syntax of the `case` statement, and using

`expr` instead of arithmetic expansion.

Resolves: #2903

Add test coverage for Xcode via `xcodebuild`

Add test for older versions of the windows sdk

Add stale object file test coverage for `CppCompile` task (#2874)

Add stale object file test coverage for `CppCompile` task

Polishing of Gradle build options (#2890)

  1. … 18 more files in changeset.
Add Details/Result to 'Build buildSrc' build operation

Rename `VersionSelector` to `VersionMatcher`

This refactor is introduced to reduce confusion: the selector corresponds to

the requested version, which can be an exact version number, a range, or

anything else. The matchers, on the other hand, match a selector. In other

words, the selector is a specification, while the matcher does the actual

work of matching.

  1. … 55 more files in changeset.
Rename `VersionSelector` to `VersionMatcher`

This refactor is introduced to reduce confusion: the selector corresponds to

the requested version, which can be an exact version number, a range, or

anything else. The matchers, on the other hand, match a selector. In other

words, the selector is a specification, while the matcher does the actual

work of matching.

Handle range of HTTP error codes the same way as timeouts

Update expectations for distribution content

Add org.gradle.console to documentation

Merge pull request #2819 from gradle/dl/xctest-component-coverage

Add test coverage for `xctest` component

    • -0
    • +10
    /subprojects/docs/src/docs/release/notes.md
link issue to ignored testcase (testng)

Convert userguide to asciidoc: plugins - signing (#2887)

    • -0
    • +296
    /subprojects/docs/src/docs/userguide/plugins.adoc
    • -382
    • +0
    /subprojects/docs/src/docs/userguide/plugins.xml
    • -0
    • +93
    /subprojects/docs/src/docs/userguide/pmdPlugin.adoc
    • -95
    • +0
    /subprojects/docs/src/docs/userguide/pmdPlugin.xml
    • -0
    • +279
    /subprojects/docs/src/docs/userguide/publishingIvy.adoc
    • -0
    • +167
    /subprojects/docs/src/docs/userguide/signingPlugin.adoc
Recognize contribution by zosrothko

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Merge pull request #2899 from zosrothko/patch-1

Eclipse: Add build/generated-resources/test to the classpath

Add build/generated-resources/test to the classpath

build/generated-resources/test needs to be added to the classpath, otherwise there is an `ExceptionInInitializerError` when looking for the resource `/org/gradle/build-receipt.properties` in `org.gradle.util.GradleVersion'

Expose bug in testng progress event logging for newer testng versions

Add test coverage for version range conflict resolution

Add org.gradle.console

Implement range intersection conflict resolution

This commit introduces a range intersection conflict resolution strategy. To deal with this, an additional flag has been added to

selectors. The flag will tell if a selector is allowed to return multiple candidates. In this case, it is expected to be called

multiple times for different matching versions. The first version checked will always be the latest.

Before this change, if 2 dependencies disagree on a range, there could be a chance that a version was selected out of the intersection.

For example, if one depends on range `[3,6]` and another depends on range `[4,8]`, then the first range selects the latest revision in

range, which is `6`, and the second version selects `8`, which is the highest version within its range. Then conflict resolution kicks

in and sees `6` and `8`. It decides to upgrade to version `8`.

This commit, on the other hand, makes sure that if a selector can have multiple valid candidates, then we remember the other candidates

as well. When we see that `6` and `8` are in conflict, we then check if those selected versions come from a selector which had multiple

possible answers. If yes, then we compute the intersection of the ranges. In our example, the intersection of `[3,6]` and `[4,8]` is

`[4,6]`. The intersection is not empty, so it means that there's actually no conflict between the two ranges, because both ranges

agree that there are possible answers.

We then select the highest version within range, which is `6`, and choose the candidate which has this as its selected component version.

This is range `[3,6]`.

Use Gradle's versions of common dependencies with JGit

Remove external source resolver temporarily

Remove unused settings loader

Support for Windows SDK 10

  1. … 5 more files in changeset.
Do not check other repositories if presence of module cannot be determined

  1. … 5 more files in changeset.
Implement integration test for issue #2891

Implement integration test for issue #2891

Unify static and generated DependencyHandler extensions

See #291

Introduce HTTP connection and socket timeout

  1. … 3 more files in changeset.