Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Convert `reporting` build script to Kotlin

  1. … 2 more files in changeset.
Convert all remaining task creation to lazy configuration

  1. … 25 more files in changeset.
Introduced the property moduleType to derive source compatibility settings

  1. … 80 more files in changeset.
Refactored Kotlin gradlebuildJava extension object into proper Gradle extension

  1. … 10 more files in changeset.
Moved grooyPlugin.gradle.kts into a buildSrc plugin

- Removed all usage of extra properties added by groovyPlugin

- Renamed to UnitTestAndCompilePlugin

- Extracted uber configuration from root and groovy script into JavaProjectsPlugin

  1. … 14 more files in changeset.
"coordinate" -> "coordinates"

  1. … 60 more files in changeset.
Move dependency constraints into a separate project

  1. … 69 more files in changeset.
Extract idiomatic test-fixtures plugin to buildSrc

Plugin is applied to all "groovy projects", see `groovyProject.gradle`.

The plugin configures the Project as a test fixtures producer if

`src/testFixtures` is a directory.

The plugin configures the Project as a test fixtures consumer according

to the `testFixtures` extension configuration.

No more Groovy Closure with optional parameters as a Project extra


Test-fixtures configuration rely on a Groovy DSL only feature that

allows to pass a collection of dependency notations when declaring

dependencies. The Kotlin DSL lacks this feature, see

A workaround has been put in place in `build-extensions.kt` in order to

move forward until this is properly fixed in the Kotlin DSL.

Signed-off-by: Paul Merlin <>

  1. … 70 more files in changeset.
Favour declarative plugin application in build scripts

  1. … 26 more files in changeset.
Changed a few more projects to use the `java-library` plugin.

  1. … 8 more files in changeset.
Changed default Java version for our projects to Java 7. Changed build scripts for those projects that still require Java 6.

  1. … 14 more files in changeset.
Changed the dependency html report to retrieve jquery from the Google repo, and use HtmlReportRenderer to manage the resources for the report.

  1. … 8 more files in changeset.
REVIEW-1961: add integtest coverage for jacoco integration in builddashboard plugin

  1. … 1 more file in changeset.
Changed the build so that it no longer uses the `groovy` configuration.

  1. … 35 more files in changeset.
use libraries.jsoup instead of a specific version of jsoup.

  1. … 1 more file in changeset.
Added documentation and applied suggestions made by Adam and Luke in the dev list

  1. … 17 more files in changeset.
Finished first implementation step of reporting design document.

  1. … 12 more files in changeset.
REVIEW-130 Moved out the help tasks implementation to a separate project.

1. The new subproject is called 'diagnostics' (follows an existing convention of the package names). New subproject contains help task implementations (including dependency report tasks). 'reporting' subproject only contans the reporting API.

2. Added the help tasks implementation on the integTestRuntime classpath for every project with integTests. This way we avoid surprises that 'help' or 'tasks' task is missing when one writes a unrelated integ test.

  1. … 148 more files in changeset.
REVIEW-71 Moved help tasks to plugin, introduced new 'reporting' project.

1. Moved all implicit tasks (help tasks) creation to a plugin. Some rename job of the plugin is still pending.

2. Introduced new 'reporting' plugin that keeps the help tasks and stuff they need. It also hosts the Reporting API so subprojects that only needs Reporting API should only depend on 'reporing' project (and not on all 'plugins'). This change means that plugins project and core project get thinner.

3. Moved the relevant integration tests to 'reporting' project. This means that when someone works on the dependency reports he may just run 'gradlew reporting:check' to validate.

  1. … 185 more files in changeset.