Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Upgrade commons-lang{->3} replacing packages

  1. … 175 more files in changeset.
Support publishing optional dependencies

This commit adds support for publishing optional dependencies on Java libraries.

For now, this is really limited to Java libraries, but potentially the API can

be extended to other types of components.

If doing so, the user can attach an outgoing configuration to a Java published

component. This configuration will be considered "optional", in the sense that:

- all its dependencies will be mapped to the runtime scope of Maven components,

but using `<optional>true</optional>`

- if using Gradle metadata, additional variants will be published alongside the

main (`api` and `runtime`) variants of the library.

It is not allowed to publish an optional feature which doesn't declare at least

one capability.

  1. … 19 more files in changeset.
Add tests for publishing Java platforms

  1. … 13 more files in changeset.
Update tests for constraints published to POM

- Verify <dependencyManagement> elements published to POM files

- Update tests to demonstrate that resolution with Maven metadata is now

more similar to resolution with Gradle metadata.

  1. … 4 more files in changeset.
Revert "Revert "Merge branch 'cc-java-library-plugin'""

This reverts commit c6cd884e1a8889fb25d26dfcfdfa79d896835e11.

  1. … 76 more files in changeset.
Revert "Merge branch 'cc-java-library-plugin'"

This reverts commit 0d442a55b445f537efbce65267ce9418fce2e7a8, reversing

changes made to 04647ab69fc8d19186cd2a78124ea74b8a89cc0f.

  1. … 76 more files in changeset.
Add support for publishing Java libraries with Maven

This commit makes sure that Java projects and Java libraries can be published using the `maven` plugin. As the project is built with Gradle,

we only need to add additional mappings for the `implementation`, `api` and `testImplementation` configurations, because the other configurations

only make sense when building, not consuming.

Those are mapped to the following Maven scopes:

- `api` is mapped to `compile`

- `implementation` is mapped to `runtime`

- `testImplementation` is mapped to `test`

The `compileOnly` and `runtimeOnly` dependency buckets are only used from within a project, so should not appear in the generated pom file.

  1. … 7 more files in changeset.
Clean up Maven test fixture

+review REVIEW-6123

  1. … 4 more files in changeset.

+review REVIEW-6123

  1. … 7 more files in changeset.
Fix for GRADLE-3440 & some improved integTests

  1. … 8 more files in changeset.
Updated maven-publish so that project dependencies correctly handle modified publication coordinates - Use new MavenDependency type instead of org.gradle.api.Dependency as API for generating POM - Map ModuleDependency->MavenDependency within MavenPublication - Added some integration test coverage for multi-project publications with modified/multiple publications

  1. … 15 more files in changeset.
REVIEW-1559: Check more details of the dependencies in published ivy.xml and pom.xml

  1. … 18 more files in changeset.
Move the maven test fixtures into their own package.

  1. … 33 more files in changeset.