Repository navigation
Document Code Genome Project repository in README - #1193
Merged
Merged
Conversation
New releases are published to artifacts.codegenomeproject.org rather than Maven Central, so document the settings.xml credentials and the repository declaration under both <repositories> and <pluginRepositories>. Replace the OSSRH snapshot repository, since CGP serves releases and snapshots from a single repository.
timtebeek
added a commit
that referenced
this pull request
Aug 26, 2026
Main meanwhile grew its own Code Genome Project publishing in #1191, but as a dual publish: Sonatype stays the deploy target and a codegenome-publish profile, activated by AWS credentials, points distributionManagement at the CGP bucket for a second deploy step in each workflow. This branch publishes solely to CGP, so the resolution keeps that single-target shape and drops the duplication it makes redundant: - pom.xml keeps CGP in the top-level distributionManagement, so the codegenome-publish profile that overrode it with the same coordinates is gone. - The s3 wagon is declared once, in main's .mvn/extensions.xml, rather than also in the pom's build extensions. - ci.yml and publish.yml drop the extra publish-*-codegenome steps, along with the Sonatype credentials and the --settings/--global-settings pair. Adopted from main: the CODEGENOME_USERNAME/CODEGENOME_TOKEN secret rename from #1197, the narrowed rollback condition keyed on steps.publish-release.outcome, and the README's CGP documentation from #1193, which covers what this branch's smaller README edit did and more.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New releases are published to
artifacts.codegenomeproject.orgrather than Maven Central, but the README still pointed users at the OSSRH snapshot repository and said nothing about how to resolve the plugin at all.This adds an "Artifact repository" section covering the
settings.xmlcredentials and the repository declaration under both<repositories>and<pluginRepositories>— both are needed, since plugin repositories resolve the plugin and its<dependencies>while project repositories resolverewrite.recipeArtifactCoordinatesand any OpenRewrite artifacts in the user's own dependency tree. Snapshots are enabled on both entries because CGP serves releases and snapshots from one repository, which also lets the Snapshots section drop its now-obsolete OSSRH<pluginRepository>. Also documents excludingcodegenomefrom a catch-all mirror, since a mirror's id won't match thecodegenomeserver and the credentials silently fail to apply.