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

    • -13
    • +0
    ./src/main/java/org/gradle/Person.java
    • -1
    • +0
    ./src/main/resources/org/gradle/resource.xml
    • -29
    • +0
    ./src/test/java/org/gradle/PersonTest.java
  1. … 7556 more files in changeset.
Split samples and snippets from each other

    • -13
    • +0
    ./src/main/java/org/gradle/Person.java
    • -1
    • +0
    ./src/main/resources/org/gradle/resource.xml
    • -29
    • +0
    ./src/test/java/org/gradle/PersonTest.java
  1. … 7556 more files in changeset.
Fix samples

* Typo in withSourcesJar() in one sample

* Java basic sample has issues creating javadoc with the asciidoclet

under recent java -> moved the with*Jars() include to another sample.

Issue #11140

  1. … 5 more files in changeset.
Fix samples

* Typo in withSourcesJar() in one sample

* Java basic sample has issues creating javadoc with the asciidoclet

under recent java -> moved the with*Jars() include to another sample.

Issue #11140

  1. … 5 more files in changeset.
Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

  1. … 25 more files in changeset.
Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

  1. … 25 more files in changeset.
Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

  1. … 24 more files in changeset.
Put Java Library Plugin forward

Instead of referencing first the Java plugin, the guide now uses the

Java Library plugin directly and clearly states that the Java plugin

should be seen as a technical layer and not something to be applied

explicitly in a build file.

  1. … 2 more files in changeset.
Put Java Library Plugin forward

Instead of referencing first the Java plugin, the guide now uses the

Java Library plugin directly and clearly states that the Java plugin

should be seen as a technical layer and not something to be applied

explicitly in a build file.

  1. … 2 more files in changeset.
Put Java Library Plugin forward

Instead of referencing first the Java plugin, the guide now uses the

Java Library plugin directly and clearly states that the Java plugin

should be seen as a technical layer and not something to be applied

explicitly in a build file.

  1. … 2 more files in changeset.
Document java extension in java plugin

* Includes moving things out of the convention content

  1. … 3 more files in changeset.
Document java extension in java plugin

* Includes moving things out of the convention content

  1. … 3 more files in changeset.
Document java extension in java plugin

* Includes moving things out of the convention content

  1. … 3 more files in changeset.
Document java extension in java plugin

* Includes moving things out of the convention content

  1. … 3 more files in changeset.
Document java extension in java plugin

* Includes moving things out of the convention content

  1. … 3 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

  1. … 34 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

  1. … 34 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

  1. … 26 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

  1. … 35 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

  1. … 34 more files in changeset.
Update 'java packaging' section and example

  1. … 2 more files in changeset.
Update 'java packaging' section and example

  1. … 2 more files in changeset.
Update 'java packaging' section and example

  1. … 2 more files in changeset.
Autodetect TestFramework if none is configure explicitly

When the TestFramework of a Test task is not configured explicitly it

used to default to `useJUnit()`. Now, the task's classpath is inspected

for a junit-platform-engine.jar or testng.jar. If one of them is found,

the task uses the JUnit Platform or TestNG to execute tests,

respectively.

Since we have internal dependencies on the JUnit Platform and TestNG,

all Test tasks in our own build are configured to `useJUnit()` and

explicitly.

  1. … 12 more files in changeset.
Doc updates: deprecations in AbstractArchiveTask

This commit contains the userguide and javadoc updates following the

deprecations in AbstractArchiveTask.

Samples are also updated to no longer use any deprecated API.

Issue #8217

  1. … 24 more files in changeset.
Convert `userguide` samples to lazy tasks API

  1. … 158 more files in changeset.
Prefer type-safe accessors for tasks

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

  1. … 31 more files in changeset.
Prefer type-safe accessors for source sets

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

  1. … 13 more files in changeset.
Prefer delegated properties where applicable

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

Let Kotlin DSL samples use configuration accessors where possible

  1. … 7 more files in changeset.