Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge pull request #6733 from gradle/eskatos/docs-kts/maven_plugin

Kotlin DSL samples for Maven Plugin chapter

Increase memory for large dependency graphs tests

The current limits make it almost impossible to use the adhoc performance

tests, as they need more memory to gather statistics.

Increase memory for large dependency graphs tests

The current limits make it almost impossible to use the adhoc performance

tests, as they need more memory to gather statistics.

Increase memory for large dependency graphs tests

The current limits make it almost impossible to use the adhoc performance

tests, as they need more memory to gather statistics.

Increase memory for large dependency graphs tests

The current limits make it almost impossible to use the adhoc performance

tests, as they need more memory to gather statistics.

Increase memory for large dependency graphs tests

The current limits make it almost impossible to use the adhoc performance

tests, as they need more memory to gather statistics.

Use our repackaged groovy-all.jar everywhere, even in buildSrc

Rebaseline JavaFirstUsePerformanceTest

All the `largeJavaMultiproject` cases seem to have regressed. That may

be related to https://github.com/gradle/gradle-private/issues/1502.

Rebaseline configure largeJavaMultiProject{KotlinDsl}

Both projects show some regressions. Rebaselining to unblock `master`

so we can investigate.

Add another cross build performance test

Add another cross build performance test

Remove unused improve pom support flags

  1. … 5 more files in changeset.
Remove unused improve pom support flags

  1. … 5 more files in changeset.
Remove unused improve pom support flags

  1. … 5 more files in changeset.
Remove unused improve pom support flags

  1. … 5 more files in changeset.
Remove unused improve pom support flags

  1. … 5 more files in changeset.
Terminate process forcibly if it doesn't respond

Give processes a 1s grace period to do an orderly

shutdown. If they are unresponsive, terminate them

forcibly to ensure all its resources are released.

Terminate process forcibly if it doesn't respond

Give processes a 1s grace period to do an orderly

shutdown. If they are unresponsive, terminate them

forcibly to ensure all its resources are released.

Disconnect streams in the inverse order they are connected

Otherwise there is a time window where the worker process

can no longer read its input, but can still complain about

that on its output stream. This leads to unwanted user-facing

error logging for something that is completely normal.

Disconnect streams in the inverse order they are connected

Otherwise there is a time window where the worker process

can no longer read its input, but can still complain about

that on its output stream. This leads to unwanted user-facing

error logging for something that is completely normal.

Remove cross version performance tests

We want to know if dexing transforms are faster than dexing tasks -

no need to compare that between Gradle versions.

Remove cross version performance tests

We want to know if dexing transforms are faster than dexing tasks -

no need to compare that between Gradle versions.

Remove build.id system property

Remove build.id system property

Ordering guarantee for ComponentSelectionRules

Previously, rules were not ordered but separated into two groups: with

and without extra parameters. As the extra parameter approach is about

to be deprecated, let's make the rule execution have some more ordering

guarantee.

Issue #6607

Ordering guarantee for ComponentSelectionRules

Previously, rules were not ordered but separated into two groups: with

and without extra parameters. As the extra parameter approach is about

to be deprecated, let's make the rule execution have some more ordering

guarantee.

Issue #6607

Ordering guarantee for ComponentSelectionRules

Previously, rules were not ordered but separated into two groups: with

and without extra parameters. As the extra parameter approach is about

to be deprecated, let's make the rule execution have some more ordering

guarantee.

Issue #6607

Ordering guarantee for ComponentSelectionRules

Previously, rules were not ordered but separated into two groups: with

and without extra parameters. As the extra parameter approach is about

to be deprecated, let's make the rule execution have some more ordering

guarantee.

Issue #6607

Ordering guarantee for ComponentSelectionRules

Previously, rules were not ordered but separated into two groups: with

and without extra parameters. As the extra parameter approach is about

to be deprecated, let's make the rule execution have some more ordering

guarantee.

Issue #6607

Ordering guarantee for ComponentSelectionRules

Previously, rules were not ordered but separated into two groups: with

and without extra parameters. As the extra parameter approach is about

to be deprecated, let's make the rule execution have some more ordering

guarantee.

Issue #6607