gradlew

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bump to latest nightly

  1. … 2 more files in changeset.
Revert change to `gradlew`

Revert change to `gradlew`

Update wrapper to latest nightly

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

  1. … 1 more file in changeset.
Update wrapper to latest nightly

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

  1. … 1 more file in changeset.
Update to 5.5.1 nightly

  1. … 2 more files in changeset.
Update to latest nightly

  1. … 2 more files in changeset.
Undo changes to the generated gradlew

Merge branch 'rv/issues/2903' of https://github.com/robinverduijn/gradle into sg/merges/pr-2904

  1. … 1 more file in changeset.
Update to latest nightly

  1. … 3 more files in changeset.
DEBUG

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

  1. … 2 more files in changeset.
Move kotlin-dsl in a sub directory

  1. … 1579 more files in changeset.
Regenerate wrapper script

  1. … 2 more files in changeset.
Bump to wrapper to latest nightly

  1. … 3 more files in changeset.
Lower memory for the client in our wrapper script

  1. … 1 more file in changeset.
Lower and limit build client jvm memory consumption

See #504

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

  1. … 1 more file in changeset.
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

  1. … 1 more file in changeset.
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

  1. … 1 more file in changeset.
Update wrapper script

  1. … 1 more file in changeset.
Increase memory for the daemon

The Gradle build needs more than 1G for some more demanding tasks

like a parallel `quickCheck`.

This change also reduces the client VM memory to something reasonable.

It was set to 2G before because we were running the build in the client

VM on CI. Instead we will now be forking single-use daemons on CI, which

only adds ~500ms per build and interoperates better with the memory being

defined in gradle.properties.

  1. … 9 more files in changeset.
Remove space between parenthesis which is interpreted by `zsh`

  1. … 1 more file in changeset.
Revert "Set wrapper client and daemon memory differently"

Looks like the nightly wrapper promotion job ran out of permGen with

this change.

This reverts commit 1b4f303643c99e336fb703679bf108c7ac156016.

  1. … 4 more files in changeset.
Set wrapper client and daemon memory differently

  1. … 4 more files in changeset.
Update Gradle wrapper

  1. … 2 more files in changeset.
Update wrapper script instead of using gradle.properties

  1. … 5 more files in changeset.
Do not escape JVM options when reading them from environment variables

This changes the interpretation of line breaks. This corresponds to how

we accessed them in Gradle 3.1 and earlier, which was:

`eval splitJvmOpts $DEFAULT_JVM_OPTS $JAVA_OPTS $GRADLE_OPTS`

  1. … 2 more files in changeset.
Do not escape JVM options when reading them from environment variables

This changes the interpretation of line breaks. This corresponds to how

we accessed them in Gradle 3.1 and earlier, which was:

`eval splitJvmOpts $DEFAULT_JVM_OPTS $JAVA_OPTS $GRADLE_OPTS`

  1. … 2 more files in changeset.
Allow double quotes to be used inside start script arguments

The new argument handling in start scripts introduced with Gradle 3.2

(#621) uses double quotes (") to escape arguments. This breaks the usage

of double quotes inside of an argument. E.g.: `'-DFOO="bar < baz"'`

This is fixed by checking if either (") or (') is already used and

using the corresponding other character for escaping. The solution is

adopted from: www.etalabs.net/sh_tricks.html (Working with arrays)

Issue: #865

  1. … 5 more files in changeset.
Allow double quotes to be used inside start script arguments

The new argument handling in start scripts introduced with Gradle 3.2

(#621) uses double quotes (") to escape arguments. This breaks the usage

of double quotes inside of an argument. E.g.: `'-DFOO="bar < baz"'`

This is fixed by checking if either (") or (') is already used and

using the corresponding other character for escaping. The solution is

adopted from: www.etalabs.net/sh_tricks.html (Working with arrays)

Issue: #865

  1. … 5 more files in changeset.