Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use linked hash set for merge set

Bump `kotlin-dsl` plugin version

Fix groovy compiler on windows

Fix groovy compiler on windows

Fix groovy compiler on windows

Fix actual problems with our own task declarations

Use standard Inject annotation in test

Test for conflicting annotations on field and method

Document how the type annotation metadata store works

Make the detection of Groovy-generated getters generic

We don't want DefaultTypeAnnotationMetadataStore to depend directly on Groovy. Instead, we can inject code that detects Groovy generated 'is'-getters.

Remove unused test class

Also split another test case to better capture what's going on with ignored properties.

Allow parameter isolation to work with custom classloaders

Allow parameter isolation to work with custom classloaders

Allow parameter isolation to work with custom classloaders

Make PropertyMetadata API nicer and safer to work with

Fix macOS CI failures for multiple Xcode installation for C++

Handle cases when we have both 'is'-getters and 'get'-getters

Groovy generates both an 'is' and a 'get'-getter for boolean properties, and we shouldn't warn in this case. However, if the user defines both getter methods, we should require at least one of them to be explicitly ignored.

We need to figure out which method we need to call to get the value of the property. In the Groovy-generated case we can safely pick the 'get'-getter, because they both do exactly the same. In the user-specified case we need to be told which (if any) to use, as we have no means to make this decision on our own.

Align Kotlin parser compiler configuration with `kotlin-library` plugin

for the binary compatibility check

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

Merge pull request #9188 from gradle/lacasseio/fix-swift-failures

Use `-fPIC` for C++ static library with Swift 4.1+ tool chain

Allow Groovy-generated boolean getters to exist without warning

Refine isKotlinInternal metadata query

by clarifying the visitation flow, checking members flags only when

their jvm signature matches

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

Refine binary compatibility check types

by removing spurious printlns

and cleaning up imports

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

Remove unnecessary newline

Test warning when ignored property has other annotations

Test warnings for annotated non-getter methods

Handle Inject annotation on fields

Unlike other property type annotations, we allow `@Inject` to be present on fields without a getter.

Merge pull request #9192 from gradle/pledbrook/start-scripts-docs

Fix reference to `createStartScripts` task in docs

Fix reference to `createStartScripts` task in docs

The Application Plugin reference page has one mention of a `createStartScripts`

that should be `startScripts`.

Update released version to latest snapshot

Update library versions in build init to latest for 5.6