Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Split the `signing` module

This commit splits the `signing` module into another `security`

project so that we can reuse some code for dependency verification.

It's worth noting that some of the classes had to remain in the `plugins`

package because they were public APIs.

Further effort to split them out may be done later.

    • -2
    • +3
    /subprojects/logging/logging.gradle.kts
    • -0
    • +46
    /subprojects/security/security.gradle.kts
  1. … 58 more files in changeset.
Add missing 'ToBeFixedForInstantExecution'

Add missing 'ToBeFixedForInstantExecution'

Upgradle to wrapper with latest file watching changes

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Upgradle to wrapper with latest file watching changes

The wrapper is from #11660

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Upgradle to wrapper with latest file watching changes

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Add vfs retention tests for Windows and macOs as well (#11672)

Add vfs retention tests for Windows and macOs as well

Add vfs retention tests for Windows and macOs as well

    • -1
    • +5
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Introduce `providers.fileContent(regularFileProvider).getAsText()` API

Introduce `providers.fileContents(regularFileProvider).getAsText()` API

Add TODOs

Merge remote-tracking branch 'origin/green-master' into lptr/vfs/handle-watcher-overflow

Merge pull request #11667 from gradle/lacasseio/update-sample-plugin

Update sample plugin to fix execution flag on wrappers

Merge pull request #11670 from gradle/lacasseio/filter-fix

Always honor excludes when using JUnit platform

Wait more for file system changes so they are picked up even on Windows

Use maven-publish plugin [WIP]

    • -0
    • +36
    /subprojects/api/api.gradle.kts
Temporary workaround for protobuf & instant execution

Note: doesn't work from clean builds

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

Debug log each change picked up since last build

Bump native-platform to version with non-enum JNI

Fix NGTest exclude test filter

Add test for the exclude filter fix for JUnitPlatform

Fix direct get resource for GCS

It looks like this code path was never properly tested and working

since this was implemented. It was only working for the case

where we have a populated cache (Maven local) and probe for

metadata before downloading.

Remove extra newline

Update to native platform 0.20

Create a different verification file if dry run is on

This commit is another usability issue: this allows simulating

the write of a verification file by resolving all configurations,

but instead of modifying the file it actually generates a different

one which can then be used for diff'ing.

This can be useful whenever the user wants to have comments and a

specific order in their verification file and want to merge the

diff by hand. It's also useful to avoid having to actually execute

the build to check if all configurations would be ok.

Create a different verification file if dry run is on

This commit is another usability issue: this allows simulating

the write of a verification file by resolving all configurations,

but instead of modifying the file it actually generates a different

one which can then be used for diff'ing.

This can be useful whenever the user wants to have comments and a

specific order in their verification file and want to merge the

diff by hand. It's also useful to avoid having to actually execute

the build to check if all configurations would be ok.

Ignore trusted modules when writing the file

This is particularly useful when you want to ignore some modules

in the output file (for example, the native-platform snapshots)

but don't want them to appear in the verification file either.

The checking is also slightly changed so that we would only check

if a module is trusted if there's actually a verification error.

Ignore trusted modules when writing the file

This is particularly useful when you want to ignore some modules

in the output file (for example, the native-platform snapshots)

but don't want them to appear in the verification file either.

The checking is also slightly changed so that we would only check

if a module is trusted if there's actually a verification error.

Test resolving roots for OSs separately

Update sample plugin to fix execution flag on wrappers