Skip to content

Conversation

@spbolton
Copy link
Contributor

Description

Add optional Java version and Maven compiler override parameters to reusable CI/CD workflows, enabling builds with different Java versions and bytecode targets without modifying .sdkmanrc. Includes artifact naming isolation, Docker tag suffixes, and backward compatibility.

Changes

  • [List the main changes made]

Testing

  • [Describe testing approach]

Closes #34586

Issue: [TASK] Add Java override parameters to core CICD a

Add optional Java version and Maven compiler override parameters to
reusable CI/CD workflows, enabling builds with different Java versions
and bytecode targets without modifying .sdkmanrc.

Changes:
- Add java-version, maven-compiler-release, artifact-suffix inputs to
  trunk, nightly, and release workflows
- Implement artifact naming isolation (e.g., maven-repo-java25)
- Apply Docker tag suffixes for Java variant builds
- Skip CLI native builds when java-version is overridden (GraalVM/Quarkus
  compatibility)
- Suppress 'latest' Docker tag for non-default Java builds
- Auto-default maven.compiler.release from Java major version
- Add actionlint and shellcheck to mise.toml for workflow validation

Backward compatible: when no override inputs provided, workflows behave
identically to current behavior.

Closes #34586

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Since CLI builds are entirely skipped when java-version is overridden
(GraalVM/Quarkus compatibility), the java-suffix parameters in
deploy-cli-npm and deploy-jfrog actions are never used.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

[TASK] Add Java override parameters to core CI/CD actions

1 participant