Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Prototype for replacing Buildship custom classpath filtering with Eclipse test sources

  1. … 3 more files in changeset.
Replace Buildship custom classpath filtering with the Eclipse 'test sources' feature

The custom classpath filtering is confusing to our users and prone

to errors. We decided to replace it with Eclipse's built-in test

source feature which was introduced in Eclipse Photon:

https://www.eclipse.org/eclipse/news/4.8/jdt.php#jdt-test-sources

  1. … 4 more files in changeset.
Prototype for replacing Buildship custom classpath filtering with Eclipse test sources

  1. … 5 more files in changeset.
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.

This commit validates the configured publications (using `afterEvaluate`), and fails the

build with a helpful message if 2 publications share the same type and target coordinates.

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.

This commit validates the configured publications (using `afterEvaluate`), and fails the

build with a helpful message if 2 publications share the same type and target coordinates.

Fixes #3835

Validate repository name when publishing

The `repository.name` value is used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name"

being used for repositories configured for publication.

Fixes #5533

Validate repository name when publishing

The `repository.name` value is used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name"

being used for repositories configured for publication.

Fixes #5533

Validate publication and repository names when publishing

The repository and publication names are used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name" being used.

Fixes #5533

Validate repository name when publishing

The `repository.name` value is used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name"

being used for repositories configured for publication.

Fixes #5533

Validate repository name when publishing

The `repository.name` value is used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name"

being used for repositories configured for publication.

Fixes #5533

Validate publication and repository names when publishing

The repository and publication names are used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name" being used.

Fixes #5533

Validate repository name when publishing

The `repository.name` value is used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name"

being used for repositories configured for publication.

Fixes #5533

Validate repository name when publishing

The `repository.name` value is used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name"

being used for repositories configured for publication.

Fixes #5533

Validate repository name when publishing

The `repository.name` value is used to construct task names when publishing.

This change adds validation to prevent invalid names such as "bad:name"

being used for repositories configured for publication.

Fixes #5533

Use Java8 features in publishing plugins

Use Java8 features in publishing plugins

Use Java8 features in publishing plugins

Use Java8 features in publishing plugins

Use Java8 features in publishing plugins

Use Java8 features in publishing plugins

Use Java8 features in publishing plugins

Fix checkstyle issues

Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009