Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make BuildClassPath more idiomatic

Make BuildClassPath more idiomatic

Polish `KotlinScript` and family

- Better and more uniform names

Polish `KotlinScript` and family

- Better and more uniform names

Do not nag on deprecated archivePath until Kotlin plugin is updated

Do not nag on deprecated archive task properties until Kotlin plugin is updated

- archivePath

- archiveName

- classifier

- appendix

Do not nag on deprecated archivePath until Kotlin plugin is updated

Do not nag on deprecated archive task properties until Kotlin plugin is updated

- archivePath

- archiveName

- classifier

- appendix

Do not nag on deprecated archivePath until Kotlin plugin is updated

Do not nag on deprecated archivePath until Kotlin plugin is updated

Do not nag on deprecated archivePath until Kotlin plugin is updated

Do not nag on deprecated archive task properties until Kotlin plugin is updated

- archivePath

- archiveName

- classifier

- appendix

Do not nag on deprecated archivePath until Kotlin plugin is updated

Do not nag on deprecated archive task properties until Kotlin plugin is updated

- archivePath

- archiveName

- classifier

- appendix

Compile CUnit sample for x64 on macOS

Compile CUnit sample for x64 on macOS

Compile CUnit sample for x64 on macOS

Compile CUnit sample for x64 on macOS

Do not copy list

Remove spurious space

Do not copy list

Do not copy list

Reduce visibility

Let precompiled project scripts support the Kotlin script API

Restore `KotlinInitScript` template

Restore `KotlinBuildScript` template

Split cross version tests by task

    • -7
    • +3
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Do not define scope for dependencyManagement entries

The semantics between the configuration of a constraint in Gradle and the scope

of a declaration in dependencyManagement in Maven are fundamentally

different.

Given this, Gradle will no longer attempt to define a scope for

dependencyManagement entries when creating POM files.

The only exception is the import scope as it carries special meaning.

Fixes #10878

Do not define scope for dependencyManagement entries

The semantics between the scope of a constraint in Gradle and the scope

of a declaration in dependencyManagement in Maven are fundamentally

different.

Given this, Gradle will no longer attempt to define a scope for

dependencyManagement entries when creating POM files.

The only exception is the import scope as it carries special meaning.

Fixes #10878

Do not define scope for dependencyManagement entries

The semantics between the configuration of a constraint in Gradle and the scope

of a declaration in dependencyManagement in Maven are fundamentally

different.

Given this, Gradle will no longer attempt to define a scope for

dependencyManagement entries when creating POM files.

The only exception is the import scope as it carries special meaning.

Fixes #10878