Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Enable Java 8 inspections

    • -22
    • +5
    /.idea/inspectionProfiles/Gradle.xml
Enable Java 8 inspections

    • -22
    • +5
    /.idea/inspectionProfiles/Gradle.xml
Enable Java 8 inspections

    • -22
    • +5
    /.idea/inspectionProfiles/Gradle.xml
Enable Java 8 inspections

    • -22
    • +44
    /.idea/inspectionProfiles/Gradle.xml
Enable Java 8 inspections

    • -22
    • +44
    /.idea/inspectionProfiles/Gradle.xml
Do not run the constructors for beans deserialized from the instant execution cache.

Do not run the constructors for beans deserialized from the instant execution cache.

Serialize the fields of beans with zero arg constructors to the instant execution cache.

Serialize the fields of beans with zero arg constructors to the instant execution cache.

Split out the strategy for serializing the fields of a `Task` object, so that it can be reused to serialize the fields of a bean.

Split out the strategy for serializing the fields of a `Task` object, so that it can be reused to serialize the fields of a bean.

Do not attempt to serialize values that reference certain Gradle types that hold project state, such as `Project` or `Task` instance to the instant execution cache.

Do not attempt to serialize values that reference certain Gradle types that hold project state, such as `Project` or `Task` instance to the instant execution cache.

Update released version to latest snapshot

Update version to 5.7

Clean release notes and welcome message for 5.7

    • -3
    • +3
    /subprojects/docs/src/docs/release/notes.md
Publish 5.5-20190518024614+0000

Split up `InstantExecutionIntegrationTest` into some separate classes.

Split up `InstantExecutionIntegrationTest` into some separate classes.

Merge remote-tracking branch 'origin/release'

* origin/release:

Bump to latest 5.5 nightly

Remove unused file

Improve detection of duplicate publications

- Validate duplicate publications accross projects

- Do not fail when same repository is defined multiple times

Improve detection of duplicate publications

- Validate duplicate publications accross projects

- Do not fail when same repository is defined multiple times

Improve detection of duplicate publications

- Validate duplicate publications accross projects

- Do not fail when same repository is defined multiple times

Improve detection of duplicate publications

- Validate duplicate publications accross projects

- Do not fail when same repository is defined multiple times

Improve detection of duplicate publications

- Validate duplicate publications accross projects

- Do not fail when same repository is defined multiple times

Improve detection of duplicate publications

- Validate duplicate publications accross projects

- Do not fail when same repository is defined multiple times

Improve detection of duplicate publications

- Validate duplicate publications accross projects

- Do not fail when same repository is defined multiple times

Improve detection of duplicate publications

- Validate duplicate publications accross projects

- Do not fail when same repository is defined multiple times

Prohibit multiple publications of the same type with the same target coordinates

When defining multiple publications, it is easy to accidentally give 2 publications the

same module coordinates. In particular, if no publication defines specific coordinates,

they all share the same default coordinates for the project.

When published, the second one published to a repository will overwrite the previous,

often resulting in an unusable published module.

There are valid use cases for configuring multiple publications, but only publishing one

of them (the "maven-publish/conditional-publishing" sample does just this). As such, we

need to validate late, only when a publication is actually published.

This commit validates each publication as it is published, failing the build with a

helpful message if a publication with the same coordinates has already been published

to the same repository. At this stage, the check is only performed on publications within

a single project.

Fixes #3835

Prohibit multiple publications of the same type with the same target coordinates

When defining multiple publications, it is easy to accidentally give 2 publications the

same module coordinates. In particular, if no publication defines specific coordinates,

they all share the same default coordinates for the project.

When published, the second one published to a repository will overwrite the previous,

often resulting in an unusable published module.

There are valid use cases for configuring multiple publications, but only publishing one

of them (the "maven-publish/conditional-publishing" sample does just this). As such, we

need to validate late, only when a publication is actually published.

This commit validates each publication as it is published, failing the build with a

helpful message if a publication with the same coordinates has already been published

to the same repository. At this stage, the check is only performed on publications within

a single project.

Fixes #3835