Jendrik Johannes

Add clarifying comment about realizing artifact tasks that do not run

Configure Javadoc and sources separately and create tasks only on demand

    • -2
    • +3
    /subprojects/docs/src/docs/release/notes.md
  1. … 20 more files in changeset.
Make task creation parallel save

Configure Javadoc and sources separately and create tasks only on demand

    • -2
    • +3
    /subprojects/docs/src/docs/release/notes.md
  1. … 12 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

    • -2
    • +3
    /subprojects/docs/src/docs/release/notes.md
  1. … 21 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

    • -2
    • +3
    /subprojects/docs/src/docs/release/notes.md
  1. … 20 more files in changeset.
Compute the name of PublishArtifactLocalArtifactMetadata lazily

In case where the publish artifact is of type 'LazyPublishArtifact',

this broke the laziness.

Compute the name of PublishArtifactLocalArtifactMetadata lazily

In case where the publish artifact is of type 'LazyPublishArtifact',

this broke the laziness.

Restructure parts about components and artifacts in publishing chapter

- Start with adjusting components from java plugins

(most common and simple use case, can be used to add custom artifacts,

includes updated 'javadoc' sample now)

- Extra section on creating completely new components

- Only one section about artifacts, starting with the warning,

recommending to not mix components and artifacts

Restructure parts about components and artifacts in publishing chapter

- Start with adjusting components from java plugins

(most common and simple use case, can be used to add custom artifacts,

includes updated 'javadoc' sample now)

- Extra section on creating completely new components

- Only one section about artifacts, starting with the warning,

recommending to not mix components and artifacts

Add Javadoc/sources publishing changes to notes and upgrading guide

    • -0
    • +15
    /subprojects/docs/src/docs/release/notes.md
Add Javadoc/sources publishing changes to notes and upgrading guide

    • -0
    • +15
    /subprojects/docs/src/docs/release/notes.md
Integration test coverage for resolving Java 'documentation' variants

Integration test coverage for resolving Java 'documentation' variants

Category.DOCUMENTATION is compatible with other category types

If one requests documentation, we want to be lenient. That is,

if a publication does not contain any documentation, we don't want

to fail. Instead, we now just return what we have (i.e. the main

artifact) which can also be used for documentation purpose in

the absence of other documentation. E.g. an IDE can de-compile

the bytecode if the source code is missing.

This change is also needed to make local matching work. Since

the documentation variants are secondary variants to a primary

LIBRARY variant, the matching would fail on the incompatible

primary variant before even considering the secondary variants

for selection.

Category.DOCUMENTATION is compatible with other category types

If one requests documentation, we want to be lenient. That is,

if a publication does not contain any documentation, we don't want

to fail. Instead, we now just return what we have (i.e. the main

artifact) which can also be used for documentation purpose in

the absence of other documentation. E.g. an IDE can de-compile

the bytecode if the source code is missing.

This change is also needed to make local matching work. Since

the documentation variants are secondary variants to a primary

LIBRARY variant, the matching would fail on the incompatible

primary variant before even considering the secondary variants

for selection.

Fix environment specific test expectation

Fix environment specific test expectation

Adjust expected output: GMM is now generated after artifacts are created

Adjust expected output: GMM is now generated after artifacts are created

Update 'java packaging' section and example

Update 'java packaging' section and example

Remove 'uploadArchives' as documented option for Java project publishing

Remove 'uploadArchives' as documented option for Java project publishing

Update 'complete example' section in ivy publishing chapter

Update 'complete example' section in ivy publishing chapter

Documentation variants are always marked as optional

Otherwise, they would be extended by 'default' in ivy metadata.

Documentation variants are always marked as optional

Otherwise, they would be extended by 'default' in ivy metadata.

Expect 'javadoc' and 'sources' variants in outgoing variants report

Expect 'javadoc' and 'sources' variants in outgoing variants report