Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix ArchiveTreePerformanceTest

Split prerequisites and limitations into two sections

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

Split prerequisites and limitations into two sections

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

Enhance extra properties section demonstrating multiproject builds usage

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

Enhance extra properties section demonstrating multiproject builds usage

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

Refine first sentence

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

Refine first sentence

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

Lower memory limits on our integration tests

Adjust memory settings in our integration tests

Adjust memory settings in our integration tests

Lower memory limits on our integration tests

Lower memory limits on our integration tests

Adjust memory settings in our integration tests

Adjust memory settings in our integration tests

Adjust memory settings in our integration tests

Adjust memory settings in our integration tests

Adjust memory settings in our integration tests

Limit memory for worker processes by default

Our workers for compilation, testing etc. had no default

memory settings until now, which mean that we would use

the default given by the JVM, which is 1/4th of system memory

in most cases. This is way too much when running with a high

number of workers. Limiting this to 256m should be enough for

small to medium sized projects. Larger projects will have to

tweak this value.

Limit memory for worker processes by default

Our workers for compilation, testing etc. had no default

memory settings until now, which mean that we would use

the default given by the JVM, which is 1/4th of system memory

in most cases. This is way too much when running with a high

number of workers. Limiting this to 256m should be enough for

small to medium sized projects. Larger projects will have to

tweak this value.

Limit memory for worker processes by default

Our workers for compilation, testing etc. had no default

memory settings until now, which mean that we would use

the default given by the JVM, which is 1/4th of system memory

in most cases. This is way too much when running with a high

number of workers. Limiting this to 256m should be enough for

small to medium sized projects. Larger projects will have to

tweak this value.

Limit memory for worker processes by default

Our workers for compilation, testing etc. had no default

memory settings until now, which mean that we would use

the default given by the JVM, which is 1/4th of system memory

in most cases. This is way too much when running with a high

number of workers. Limiting this to 256m should be enough for

small to medium sized projects. Larger projects will have to

tweak this value.

Refactor code to avoid calling `transform(null)`

Because the API is not supposed to be called with nulls.

Refactor code to avoid calling `transform(null)`

Because the API is not supposed to be called with nulls.

Lower memory for the Gradle daemon by default

We have made lots of memory usage improvements to Gradle,

so 512m will be enough for small-medium sized projects.

The assumption here is that power users with large projects

are much more likely to tweak these settings than peole just

getting started.

Also this change limits the metaspace on Java8+, so that memory

leaks in plugins don't go unnoticed.

Lower memory for the Gradle daemon by default

We have made lots of memory usage improvements to Gradle,

so 512m will be enough for small-medium sized projects.

The assumption here is that power users with large projects

are much more likely to tweak these settings than peole just

getting started.

Also this change limits the metaspace on Java8+, so that memory

leaks in plugins don't go unnoticed.

Lower memory for the Gradle daemon by default

We have made lots of memory usage improvements to Gradle,

so 512m will be enough for small-medium sized projects.

The assumption here is that power users with large projects

are much more likely to tweak these settings than peole just

getting started.

Also this change limits the metaspace on Java8+, so that memory

leaks in plugins don't go unnoticed.

Lower default memory for the client VM

This VM is only there to display some log messages

by default and thus shouldn't need a lot of memory.

There is the corner case of running the build directly

inside the client VM with --no-daemon. In that case some

users may have to adjust their GRADLE_OPTS environment

variable to accomodate their project.

Lower default memory for the client VM

This VM is only there to display some log messages

by default and thus shouldn't need a lot of memory.

There is the corner case of running the build directly

inside the client VM with --no-daemon. In that case some

users may have to adjust their GRADLE_OPTS environment

variable to accomodate their project.

Lower default memory for the client VM

This VM is only there to display some log messages

by default and thus shouldn't need a lot of memory.

There is the corner case of running the build directly

inside the client VM with --no-daemon. In that case some

users may have to adjust their GRADLE_OPTS environment

variable to accomodate their project.

Remove `@Nullable` for backwards compatibility with Kotlin API