Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add test case showing limitation of the current implementation of capabilities

The current implementation of "capability discovery" works well if everyone agrees on the version

to use. However, if they do not, but that a module which gave a preference is evicted (by version

conflict, typically), then the constraint is still kept in memory, and we fail. This can be solved

by adding rules to remove the preference (not implemented yet).

Expose `javax.annotation` for build scripts

We already expose `javax.annotation` via `gradleApi()`.

Merge branch 'master' into hansd/buildSrcToKotlin

Merge branch 'release'

Update wrapper to 4.6-rc-2

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Polish JarPatcher and ClasspathManifestPatcher

by making unpack functions more readable

Let `configure<T> { }` and `the<T>()` extensions be available to any `ExtensionAware` type

Keep the same extensions on Project that actually also delegate to conventions

Publish 4.6-rc-2

Remove unused import

Restore previous ShadedJarCreator FileVisitor behavior

Prefer string template over concatentation

Report error whenever two modules in the graph disagree on a preference

This commit makes it an error case to have two modules provide a preference for a capability, if that preference

is not the same. Currently we don't know how to solve such a problem, in particular because preferences can be

discovered as the graph grows, and are hard to rollback.

Another fix for ciReporting.gradle

Add `@Nullable` to `@Optional` task inputs

where applicable.

  1. … 32 more files in changeset.
Fix icReporting.gradle

Polish ClasspathManifestPatcher

by turning function bodies as expressions

and simplifying some statements

and using kotlin-stdlib more

and formatting visibility modifiers

Support capabilities with project dependencies

Previously, it was possible to discover and solve conflicts between published modules, or through the `capabilities` block when

declaring capabilities for external modules. With this commit, it is now possible to declare capabilities in projects that are

used during conflict resolution.

  1. … 15 more files in changeset.
Prefer plugin portal over repo.gradle.org

Polish JarPatcher

by removing spurious `this` references

and simplifying some expression

Don't iterate on configuration.files twice

Prefer Provider over Callable

Merge branch 'release'

Update build tagging plugin to 0.41

Let master use Gradle 4.5.1 and Gradle Kotlin DSL 0.14.2

Merge pull request #722 from gradle/eskatos/master/gradle-4.5.1

Fix type hierarchy for DependencyConstraintMetadataImpl

Prevent internal type leakage

Update ISSUE_TEMPLATE.md

Polish `JsoupCopyExtension`

- Prefer `filter(vararg Pair<K, V>)` over `filter(Map<K, V>)`

Use Jackson for parsing JSON in wrapper.gradle.kts

Jackson provides lightweight data-binding for Kotlin, that ends

up being simpler than using `groovy.json.JsonSlurper`.

Signed-off-by: Daz DeBoer <daz@gradle.com>

Cast Json object to Map rather than relying on withGroovyBuilder

Signed-off-by: Daz DeBoer <daz@gradle.com>