Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use maven-publish in init plugin

When converting a Maven project, the generated build scripts now use the

`maven-publish` plugin instead of the `maven` plugin. The buildscripts

contain a single publication named “maven” that uses `components.java`.

Resolves #7952.

Add compatibility subclass for DefaultConvention

This is required as IntelliJ IDEA import uses this class.

See https://youtrack.jetbrains.com/issue/IDEA-204971

Merge branch 'release'

Merge branch 'release'

Stop daemon after processing

Genearate stack files

Fix issues

Fix bash -c

enable pid

Use perf

Remove PropertyValue

ValidatingValue is enough to capture the actual value.

  1. … 9 more files in changeset.
Clean up some tests to fix issues on windows

Change C++ init samples to use classes

Clean up DefaultDependencyHandler to use injector generated ExtensionAware

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@plexxi.com>

Merge branch 'master' into dependency-handler-as-extension-aware

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@plexxi.com>

Change namespace declarations to be compliant with older compilers

Rename {TypeProperty -> Type}Metadata{,Store}

  1. … 9 more files in changeset.
Do not use weak keys

This is unnecessary at this point.

Fix typo in Organizing Gradle Projects

Signed-off-by: Victor Jacobs <victor.jacobs@n26.com>

Prepare branch for 5.1.1 bugfix release

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Remove `propertyName` and `value` from PropertyValue

This brings PropertyValue closer to a basic ValidatingValue.

Fix named instantiator leaking memory

This commit reworks the named object instantiator so that it doesn't

leak memory, by locating the cache on the `VisibleURLClassLoader`

instance whenever possible. Previously, it retained strong references

to classes, meaning that any class loaded via a script classloader

would be strongly referenced and would prevent the loader from being

collected. With this change, the cache is now located on the loader

itself.

If, for some reason, the loader is not a known classloader, we will

still use a global cache, but this shouldn't leak memory anymore

since in this case it's likely the affected classes come from Gradle

core itself.

Fixes #8142

Polish `settings.gradle.kts`

- Replace `if (!e) throw IAE(m)` by `require(e) { m }`

- Replace `!c.contains(e)` by `e !in c`

- New line before closing parenthesis of multiline expression

Signed-off-by: Rodrigo B. de Oliveira <rodrigo@gradle.com>

Polish `settings.gradle.kts`

Signed-off-by: Rodrigo B. de Oliveira <rodrigo@gradle.com>

Enable bad header candidate test now that native-platform is updated

Touch file

Fix array issue

Revert "Update to latest nightly"

The latest nightly breaks the IDEA import, since

`DefaultConvention` moved the package and is used here:

https://github.com/JetBrains/intellij-community/blob/master/plugins/gradle/tooling-extension-impl/src/org/jetbrains/plugins/gradle/tooling/builder/ProjectExtensionsDataBuilderImpl.groovy#L50

This reverts commit 08a64806

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Support multi version

Simplify PropertyExtractor constructor