baseline-java-versions: explainJavaVersions task

[CRogers]

Before this PR

It's hard to work out which versions baseline-java-versions has chosen for each project without looking at the logs or debugging.

After this PR

==COMMIT_MSG==
baseline-java-versions: Provide an explainJavaVersions task that makes it easier to work out which target and runtime java versions have been chosen by the plugin and why.
==COMMIT_MSG==

Example output from a repo:

> Task :project-api:explainJavaVersions
target  = 21 (default value was 17 - changed by a Gradle script or plugin)
runtime = 21 (default value)
Reason: considered a library because it didn't match any other conditions that would indicate it was a distribution:
  * It did not have a distribution plugin: [com.palantir.external-publish-dist, com.palantir.publish-dist, com.palantir.sls-java-service-distribution]
  * It had a publishing extension, indicating *something* that isn't a known distribution type is being published. The publications in this extensions are [auditSchema, conjure]
Despite not having any library publish plugins ([com.palantir.external-publish-jar, com.palantir.publish-jar]), this is conservatively regarded as a library for safety.

> Task :project-adjudicator-provider:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-adjudicator-api:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-adjudicator-impl-installation:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-commons:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-adjudicator-impl-release-channel-promotion:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-internal-api:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a library because it didn't match any other conditions that would indicate it was a distribution:
  * It did not have a distribution plugin: [com.palantir.external-publish-dist, com.palantir.publish-dist, com.palantir.sls-java-service-distribution]
  * It had a publishing extension, indicating *something* that isn't a known distribution type is being published. The publications in this extensions are [auditSchema, conjure]
Despite not having any library publish plugins ([com.palantir.external-publish-jar, com.palantir.publish-jar]), this is conservatively regarded as a library for safety.

> Task :extras:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-api:project-api-objects:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a library because it has the 'com.palantir.publish-jar' plugin applied

> Task :project-api:project-api-typescript:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it has the 'com.palantir.publish-dist' plugin applied

> Task :project-api:project-api-undertow:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a library because it has the 'com.palantir.publish-jar' plugin applied

> Task :project-constraints:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-store-alta:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-internal-api:project-internal-api-objects:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-api:audited-project-api:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a library because it has the 'com.palantir.publish-jar' plugin applied

> Task :project-store-api:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a library because it didn't match any other conditions that would indicate it was a distribution:
  * It did not have a distribution plugin: [com.palantir.external-publish-dist, com.palantir.publish-dist, com.palantir.sls-java-service-distribution]
  * It had a publishing extension, indicating *something* that isn't a known distribution type is being published. The publications in this extensions are [auditSchema, conjure]
Despite not having any library publish plugins ([com.palantir.external-publish-jar, com.palantir.publish-jar]), this is conservatively regarded as a library for safety.

> Task :project-internal-api:audited-project-internal-api:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-store-api:audited-project-store-api:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :project-api:project-api-dialogue:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a library because it has the 'com.palantir.publish-jar' plugin applied

> Task :project-store-api:project-store-api-objects:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

> Task :extras:test-common:explainJavaVersions
target  = 17 (default value)
runtime = 21 (default value)
Reason: considered a distribution because it doesn't have any publishing extensions defined

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

baseline-java-versions: Provide an explainJavaVersions task that makes it easier to work out which target and runtime java versions have been chosen by the plugin and why.

Check the box to generate changelog(s)

• Generate changelog entry

Invalidated by push of 44167b8

[felixdesouza]

👍

[autorelease3]

Released 6.22.0