design-docs

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Parameter connection related code simplification

Renamings and code simplifications suggested in the pull request.

No functionality changed.

    • -164
    • +0
    ./tooling-api-parameterized-custom-models.md
  1. … 16 more files in changeset.
Remove design-docs folder

This has turned into a graveyard for ideas. It only serves

to confuse people at this point. We have found it more productive

to either

- use GitHub Epics and issues for smaller design questions

- use Google Docs for larger topics (e.g. native publishing)

These documents quickly go out of date once a feature is implemented.

They are not a replacement for good user and code documentation.

Many of the documents are about features that we never ended up

implementing. Having those documents still around might lock us

into a certain way of thinking about a problem. Instead we should

have a fresh look at it when we actually want to start working on it.

    • -278
    • +0
    ./application-plugin-improvements.md
    • -329
    • +0
    ./building-and-packaging-applications-and-libraries.md
    • -1193
    • +0
    ./component-model-for-jvm-components.md
    • -1228
    • +0
    ./continuous-delivery-for-c-plus-plus.md
  1. … 186 more files in changeset.
Introduce creation of parameterized tooling models

This commit introduces the possibility of passing parameters through the

Tooling API to the model builders in order to create models based on

information received by the client.

This feature allows plugins to register a model builder for a given

model and parameter and then build models based on the received

parameter. It is preferable to passing gradle properties for two

reasons: first convenience and second because parameters can be created

inside the BuildAction.

A new interface ToolingParameterizedModelBuilder was created and should

be extended by parameterized builders. New methods were added to the

BuildController in order to build models with parameters. In order to

keep cross version compatibility, new protocol interfaces were created.

    • -0
    • +164
    ./tooling-api-parameterized-custom-models.md
  1. … 38 more files in changeset.
Use GNU-style release flag for Java 9 compiler (#2474)

Since JDK 9 b135, only the new GNU-style option with double-dashes is supported for the "--release" flag

(see https://bugs.openjdk.java.net/browse/JDK-8160851).

  1. … 4 more files in changeset.
Use GNU-style release flag for Java 9 compiler (#2474)

Since JDK 9 b135, only the new GNU-style option with double-dashes is supported for the "--release" flag

(see https://bugs.openjdk.java.net/browse/JDK-8160851).

  1. … 4 more files in changeset.
Remove use of `Java9ClassReader`

  1. … 2 more files in changeset.
Moved ObjectInstantiationException to public API

This avoids leaking an internal exception type through the

ObjectFactory.newInstance API.

  1. … 26 more files in changeset.
Replace showing work avoided in console with showing in build result

Add some more details to spec

Break out story for declaring dependency on public API of core plugins

Add spec for exposing new Gradle API methods to DependencyHandler

    • -64
    • +112
    ./internal-apis-made-public.md
Remove some some duplicated words from gradle

    • -1
    • +1
    ./done/dependency-resolution-reporting.md
  1. … 9 more files in changeset.
remove extraneous letter

Allow running tasks before executing BuildAction

Introduce methods forTasks in tooling API's BuildActionExecuter so the

user is able to run tasks before having his BuildAction executed, in the

same connection.

This feature is useful in Android development for determining a list of

APK slipts (running some tasks) and return a model with them afterwards

so the IDE can configure the project.

  1. … 9 more files in changeset.
Update spec based on feedback

Lay out option for approaching convention mapping as public API

Some improvements to milestone 2 of Console design spec

Design specification for improved Console output (#1063)

Introduces 4 deliverable milestones

    • -0
    • +409
    ./improved-console.md
Introduce spec for turning internal API into public APIs

    • -0
    • +70
    ./internal-apis-made-public.md
Spec and test cases for removing JavaCompile stale output (#984)

Spec and test cases for removing JavaCompile stale output

  1. … 2 more files in changeset.
Update code-coverage.md

Touch up spec to reflect reality

Add spec for code coverage features

    • -0
    • +179
    ./code-coverage.md
Base design doc for JUnit Platform support

Design doc covering the problem statement for JUnit Platform support

and the related infrastructure issues. This is meant to facilitate

discussion and agreement on what should be solved in the scope of

supporting the JUnit Platform.

Issue: #828

Add spec for changing the tasks report

    • -0
    • +165
    ./task-reporting.md
Update from feedback

Update composite task execution spec

Update README.md

fix formatting

Add some possible solution ideas

initial details for task execution in a composite

    • -0
    • +159
    ./features/composite-build/task-execution/README.md
Refined design doc to be in line with integration test

The example in the integration tests and the doc should now use the same

project/module names and versions. In addition some clutter was removed

from the example, i.e. build script details that do not influence the

behaviour described in the document.

+review REVIEW-6173

    • -39
    • +33
    ./dependency-management-projectpriority.md