multiple-publications

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Always evaluate publishing block eagerly

This commit makes `enableFeaturePreview('STABLE_PUBLISHING')`

meaningless by always using the new behavior. The flag is kept for

backward compatibility.

  1. … 55 more files in changeset.
Always evaluate publishing block eagerly

This commit makes `enableFeaturePreview('STABLE_PUBLISHING')`

meaningless by always using the new behavior. The flag is kept for

backward compatibility.

  1. … 55 more files in changeset.
include Kotlin DSL sample for chapter publishing_ivy (customize-identity sample)

Signed-off-by: jnizet <jb@ninja-squad.com>

    • -2
    • +0
    ./publish-customize-identity.sample.conf
  1. … 6 more files in changeset.
Convert user manual to be generated by Asciidoctor only

This change replaces all embedded Docbook syntax from the user manual.

Asciidoctor files are now converted directly to HTML and PDF.

It not only greatly simplifies the user manual generation pipeline, but also it makes it faster.

I did the following for all user manual pages:

- [x] Adjusted links to other manual pages, DSL docs, and Javadocs where necessary.

Fixed a couple dozen broken links at least.

- [x] Convert samples XML from docbook to asciidoctor syntax

- [x] Converted wide tables to a more flexible list-based display

Important contributor differences from now on:

- Users must use a `<file>.adoc#` prefix for all cross-reference links.

This is _required_ to achieve working links in all 3 outputs: multi-page user manual, single-page user manual, and PDF.

- The manual PDF is no longer themed, and no longer has the list of examples links in the TOC.

- File names were changed from camelCased to snake_case to have a crystal clear 1-1 mapping between source to output.

- Section reference verification is now handled by Asciidoctor verbose mode.

- The single-page user manual has the same navigation as the multi-page manual for now.

- [Common Asciidoctor extensions](https://github.com/gradle/dotorg-docs/tree/master/docs-asciidoctor-extensions) are now used by Gradle Guides and the User Manual, however, the the web assets (CSS, JS, etc) are not yet merged.

These extensions are responsible for injecting the navigation and styles.

The header/footer/navigation HTML can now be found under `subprojects/docs/src/main/resources`.

  1. … 401 more files in changeset.
Rename sample config files to avoid colons in file names

    • -0
    • +2
    ./publish-customize-identity.sample.conf
    • -2
    • +0
    ./publishing_ivy:publish-customize-identity.sample.conf
  1. … 8 more files in changeset.
Externalize samples testing infrastructure

This change replaces UserGuideSamplesRunner with an external library

called sample-check. Sample discovery, execution, and normalization

is delegated to this library, with some custom normalizers remaining

in the Gradle codebase.

Samples output has become co-located with the sample code. Samples tests

must be run with Java 8+.

    • -0
    • +2
    ./publishing_ivy:publish-customize-identity.sample.conf
  1. … 782 more files in changeset.
Add a overview chapter for publishing

This commit extracts the common parts of publishing from the Maven Publish and

Ivy Publish Plugin chapters and restructures them into an overview that should

be easier for newcomers to understand.

One result is slimmer plugin reference chapters. I have also added publishing

sections to the Java and War Plugin chapters detailing the components that they

define.

Finally, I have updated the formatting in the War Plugin chapter so that it's

consistent with other plugin reference chapters.

  1. … 24 more files in changeset.
Put deferred configurable change behind a feature flag

Simply removing deferred configurable can silently break builds.

Instead we now add a feature flag and nag users to opt into the

new behavior. The flag will be the new default in Gradle 5.0.

  1. … 28 more files in changeset.
Fix Java component publishing

When we introduced the `java-library` plugin, we made sure

the published POM reflects what a downstream project in the

same build would see: `api` dependencies are exposed, `implementation`

dependencies are hidden. The legacy `compile`/`runtime` dependencies

are exposed as well for backwards compatibility.

We forgot to adjust the tests for the existing `java` plugin,

leading to a confusing difference in behavior. The `java` plugin

was still hiding the legacy `compile` and `runtime` dependencies from

consumers. This was due to a bug in the implementation of `JavaLibrary`,

which was looking for the `api` configuration instead of the `apiElements`

configuration.

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

This reverts commit c6cd884e1a8889fb25d26dfcfdfa79d896835e11.

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

This reverts commit 0d442a55b445f537efbce65267ce9418fce2e7a8, reversing

changes made to 04647ab69fc8d19186cd2a78124ea74b8a89cc0f.

  1. … 75 more files in changeset.
Fix expectations on Ivy samples integration tests

  1. … 2 more files in changeset.
Fix tests relying on buggy closure behavior

  1. … 1 more file in changeset.
Upgrade Apache Commons Collections to v3.2.2

Version 3.2.1 has a CVSS 10.0 vulnerability. That's the worst kind of

vulnerability that exists. By merely existing on the classpath, this

library causes the Java serialization parser for the entire JVM process

to go from being a state machine to a turing machine. A turing machine

with an exec() function!

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103

https://commons.apache.org/proper/commons-collections/security-reports.html

http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/

  1. … 53 more files in changeset.
Use Junit 4.12 in samples

  1. … 37 more files in changeset.
Addressing open issues for 'Make branch attribute available when publishing and resolving Ivy modules'

- Adding documentation

- Tweaking tests

+review REVIEW-5059

  1. … 4 more files in changeset.
Documentation and tweaks for 'Make branch attribute available when publishing and resolving Ivy modules' story +review REVIEW-5054

  1. … 7 more files in changeset.
use consistent spelling for `customize` throughout docs and codebase

- some minor other spelling improvements along the way

  1. … 71 more files in changeset.
Use file paths instead of file:// urls in publishing samples.

  1. … 7 more files in changeset.
Project dependencies map to a single publication of the depended-on project - For single publication, use it - For multiple publications, fail unless all publications have the same coordinates - For no publications, use the project coordinates - Added ProjectDependencyPublicationResolver to do the work of determining the coordinates to use for a project dependency

  1. … 18 more files in changeset.
Improved ivy-publish sample for multiple publications, and added test

    • -0
    • +17
    ./output/project1.ivy.xml
    • -0
    • +13
    ./output/project2-api.ivy.xml
    • -0
    • +15
    ./output/project2-impl.ivy.xml
  1. … 2 more files in changeset.
Release notes and user guide docs for customising publication identity

  1. … 2 more files in changeset.