Skip to content

Configuration for deployment to Maven Central#951

Merged
arjantijms merged 1 commit intoeclipse-ee4j:2.xfrom
dmatej:maven-central-snapshots
Jan 18, 2026
Merged

Configuration for deployment to Maven Central#951
arjantijms merged 1 commit intoeclipse-ee4j:2.xfrom
dmatej:maven-central-snapshots

Conversation

@dmatej
Copy link

@dmatej dmatej commented Jan 16, 2026

If I would have committer rights, I would push this branch to the target repository, then tested it - deployments of snapshots don't cause much problems, with testing releases it is important to avoid automatic publishing, and it is good to have access to the Maven Central account managing the target namespace.

Daily deployments to snapshots would enable possibility to refer snapshots in any other projects, test them and complain BEFORE release of Tyrus. Or even temporarily cooperate on some breaking changes.

  • Merge the branch or better create the copy of this branch in the target repository
  • Create deploy-tyrus-snapshot job on the CI, see examples.
  • Check and update all values in the configuration, carefully one by one.
  • Run the new job against the branch and check everything is in order (first for the snapshot; the release job can be updated later, if even needed).
  • Merge this PR
  • Delete the experimental branch (copy of this in the target repository)

Examples:

@arjantijms arjantijms merged commit bfc5703 into eclipse-ee4j:2.x Jan 18, 2026
3 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