build.gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Split samples and snippets

  1. … 7738 more files in changeset.
Split samples and snippets from each other

  1. … 7561 more files in changeset.
Split samples and snippets from each other

  1. … 7563 more files in changeset.
Split samples and snippets from each other

  1. … 7561 more files in changeset.
Split samples and snippets from each other

  1. … 7563 more files in changeset.
Update samples to use new Java plugin configurations

  1. … 65 more files in changeset.
Update samples to use new Java plugin configurations

  1. … 65 more files in changeset.
Update samples to use new Java plugin configurations

  1. … 65 more files in changeset.
Update samples to use new Java plugin configurations

  1. … 65 more files in changeset.
Update samples to use new Java plugin configurations

  1. … 66 more files in changeset.
Update samples to use new Java plugin configurations

  1. … 65 more files in changeset.
WIP - replace 'compile' with 'implementation' in docs

  1. … 45 more files in changeset.
Resolve from /libs-releases vs /libs-releases-local

Prior to this change, the affected build scripts resolved dependencies

from two repositories: /libs-releases-local and mavenCentral(), and in

that order. /libs-releases-local is, in Artifactory terms, a "local

repository", and it contains only the things we upload to it, e.g. our

gradle-core, gradle-logging, and other gradle-* modules. This means that

the vast majority of dependency resolution requests will fail to find

what they're looking for in /libs-release-local and will then fall back

to mavenCentral(). This is inefficient and slows down builds, because it

requires two client-side HTTP requests for almost every dependency.

This commit favors the use of the /libs-release "virtual repository",

which includes all the content from /libs-release-local, but also

proxies content from maven central (actually, it proxies content from

JFrog's JCenter, but JCenter itself is a proxy for Maven Central).

This means that just one repository declaration can be used instead of

two, and that the client build need only ever issue one HTTP request for

each dependency.

Note that one exception to the explanation above is

buildSrc/build.gradle, which is being changed from /libs to

/libs-release. This same change was recently made to the project's root

build.gradle as well, and the rationale for doing so can be found at

bf9ae865daacc4757615359586588af5b8c15909.

  1. … 7 more files in changeset.
update library versions in samples and integtests

- update slf4j + ant in samples

- groovy in samples + integtests

+review REVIEW-5443

  1. … 36 more files in changeset.
update slf4j-api dependency also in build init templates, samples, integration tests

+review REVIEW-5191

  1. … 13 more files in changeset.
Use HTTPS when talking to repo.gradle.org

+review

  1. … 14 more files in changeset.
Upgraded to slf4j-api 1.7.5

  1. … 9 more files in changeset.
Upgraded to slf4j 1.7.2.

  1. … 5 more files in changeset.
Move configuration for the daemon sample integ tests into the tests, and out of the sample.

  1. … 8 more files in changeset.
Ensure the Tooling API samples inherit the daemon settings when running the sample code.

This prevents the daemons from hanging around and ensures they use the test Gradle user home.

  1. … 7 more files in changeset.
- Cleaned up the tooling API samples to get rid of the int testing cruft. Instead, the int tests inject the things they need into the samples. - Added a sample for using the generic GradleProject model.

  1. … 10 more files in changeset.
updated all usages of slf4j from 1.6.4 to 1.6.6, and all usages of groovy 1.8.4 to 1.8.6

  1. … 4 more files in changeset.
Fix some old dynamic properties usage that I missed.

  1. … 2 more files in changeset.
Fixes to the Tooling Api suite. Changes should reduce the number of long-lived daemons on the CI boxes. This is especially important for fixing windows build as daemons on windows are more keen on locking files and hence leading to failures in cleaning the workspace. On linux it should reduce the number of daemons which might improve overall performance.

-Made sure that the samples are executed against a short-lived daemon (ttl 60 secs VS 3 hours).

-Reduced the daemon timeout from 5 mins to 1 min for the tooling api tests. This should make certain things faster & more lightweight. The daemonIntegTest is still our official daemon stress tester and it still uses 5-minute timeout.

  1. … 4 more files in changeset.
Upgraded to slf4j-api 1.6.4 and logback 1.0.0.

  1. … 4 more files in changeset.
Updated samples and int tests to use repositories.maven() instead of mavenRepo().

  1. … 19 more files in changeset.
Housekeeping - renamed the 'model' sample into 'eclipse' sample. Added some more to the sample. Added some toStrings() so that sample output is more interesting and debugging easier.

  1. … 8 more files in changeset.