Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove broken test from revert

Merge remote-tracking branch 'origin/jjohannes/release-revert' into release

* origin/jjohannes/release-revert:

Remove 'release' property (reverts #12648)

Fix broken samples

Fix broken internal link

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
More polishing of release notes and features

    • -38
    • +42
    /subprojects/docs/src/docs/release/notes.md
Merge remote-tracking branch 'origin/vv/precompiled-plugin-docs' into release

* origin/vv/precompiled-plugin-docs:

Add another test for precompiled Groovy plugins

Fix plugin application within a precompiled Groovy plugin

Update a note in precompiled Groovy plugins documentation

Update Gradle wrapper to include precompiled Groovy plugins

Fix typo in sample

Update subprojects/docs/src/docs/userguide/extending-gradle/custom_plugins.adoc

Update subprojects/docs/src/docs/userguide/extending-gradle/custom_plugins.adoc

Update subprojects/docs/src/docs/release/notes.md

Update subprojects/docs/src/docs/release/notes.md

Update subprojects/docs/src/docs/release/notes.md

Update subprojects/docs/src/docs/release/notes.md

Fix Groovy syntax in precompiled plugin sample

Rename precompiled-groovy-plugin to groovy-gradle-plugin in the docs

Link to precompiled script plugins sample from release notes

Update precompiled plugins sample to include Groovy

Add a line about running samples tests in docs README

Add a release note about precompiled Groovy plugins

Document precompiled Groovy plugins in custom_plugins userguide page

    • -0
    • +13
    /subprojects/docs/src/docs/release/notes.md
Upgradle to latest nightly

to fix #12768

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Remove 'release' property (reverts #12648)

A more high level concept for specifying Java versions will

be introduced soon.

Merge pull request #12769 from gradle/jjohannes/jpms/run-jar

Let Java Modules run as Jar so that resources are accessible

Merge pull request #12773 from gradle/wolfs/vfs/dont-fill-up-the-queue

Drop the VFS if the event queue is full

Use correct method to clear interrupted status

Always clear the queue on lost state

Clear queue when it is full

Check if consumer thread is alive

when starting watching.

Drop the VFS if the event queue is full

and never block on putting something in the event queue.

Add another test for precompiled Groovy plugins

To assert that multiple plugins can be applied within a precompiled plugin.

Merge pull request #12770 from gradle/wolfs/vfs/clean-vfs-when-starting

Clean VFS when starting watching

Merge branch 'release' into vv/precompiled-plugin-docs

Fix plugin application within a precompiled Groovy plugin

Update blackbox module test samples to run all modules as Jars

Test showing how results of a separate compile step are added to module

Add release notes for publication build identifier

Issue #11717

    • -0
    • +16
    /subprojects/docs/src/docs/release/notes.md
Document configuration of build identifier

And explain how that allows to improve build reproducibility if desired.

Issue #11717

Modular app: 'run' task uses application jar instead of classes

By default, Java expects everything that belongs to one module to be

in the same location (Jar or folder). Since in Gradle resources

or outputs from different compilation steps are in separate folders,

everything that is not in the same 'classes' folder as the

module-info.class becomes unaccessible. Hence we always use the complete

Jar now to run a module via the :run task.

Use unique plugins directories in precompiled Groovy plugins integration test

Shorten paths in precompiled Groovy plugins integration test

Initial polishing and preamble for 6.4 release notes

    • -25
    • +28
    /subprojects/docs/src/docs/release/notes.md
Move execution of `TaskExecutionGraph.whenReady()` events so that it happens as part of model configuration, rather than task execution.

This better reflects its role and also allows changes made by the event handler to be captured to the instant execution cache.

Write the listeners attached to the `Test` task to the instant execution cache.

Disable stack trace checks on JDK module test