Skip to content

LDEV-6677 1.0.0.0-BETA, publish to Maven Central and GitHub releases - #2

Merged
michaeloffner merged 1 commit into
mainfrom
LDEV-6677-beta
Oct 23, 2026
Merged

michaeloffner merged 1 commit into
mainfrom
LDEV-6677-beta

Conversation

@GianTschingt

Copy link
Copy Markdown
Contributor

LDEV-6677

First BETA of the Lucee 9 http extension.

  • version 1.0.0.0-ALPHA → 1.0.0.0-BETA (pom.xml, CHANGELOG)
  • the Lucee versions to test with come only from the variable LUCEE_TEST_VERSIONS_9, validated in the setup job, no hardcoded fallback version
  • deploy needs [setup, build-and-test] and runs only for push / workflow_dispatch on the default branch after the tests passed, never for pull requests or other branches. SNAPSHOT deploys, ALPHA only installs, final / BETA / RC go to Maven Central
  • Maven 3.9.16 is pinned for the deploy (Maven 3.10.0 on ubuntu-latest stages maven-metadata-local.xml in the bundle and Central rejects it with "Bundle has content that does NOT have a .pom file"), same as the other extensions
  • new github-release job like the other extensions: creates the release <version> with the full and lite .lex files, BETA/RC as pre-release (not latest), nothing for SNAPSHOT / ALPHA

Tests are unchanged. The deploy and the release only run after merge.

…itHub pre-release from the default branch after the tests, Lucee test versions only from LUCEE_TEST_VERSIONS_9, pin Maven 3.9.16 for the Central deploy
@michaeloffner
michaeloffner merged commit 0f2b9b7 into main Oct 23, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants