Switch to Sonatype central plugin and disable publishing for examples#15
Switch to Sonatype central plugin and disable publishing for examples#15mercyblitz merged 2 commits intoreleasefrom
Conversation
Replace the old maven-deploy-plugin entry with org.sonatype.central:central-publishing-maven-plugin and update its config from <skip>true</skip> to <skipPublishing>false</skipPublishing>. This switches the build to use Sonatype's central publishing plugin and enables publishing to Maven Central instead of skipping deployment.
Set <skipPublishing>true</skipPublishing> in microsphere-logging-examples/pom.xml for the central-publishing-maven-plugin to prevent the examples module from being published and avoid accidental release of example artifacts.
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
🤖 Augment PR SummarySummary: Updates the examples module’s build publishing configuration to align with Sonatype Central. Changes:
🤖 Was this summary useful? React with 👍 or 👎 |
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
| <plugin> | ||
| <artifactId>maven-deploy-plugin</artifactId> | ||
| <groupId>org.sonatype.central</groupId> | ||
| <artifactId>central-publishing-maven-plugin</artifactId> |
There was a problem hiding this comment.
This plugin entry doesn’t specify a <version>/<extensions>true</extensions> here; if those aren’t inherited via pluginManagement, Maven can resolve an unintended plugin version (or not inject the extension), so skipPublishing may not be applied as expected.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| <artifactId>central-publishing-maven-plugin</artifactId> | ||
| <configuration> | ||
| <skip>true</skip> | ||
| <skipPublishing>true</skipPublishing> |
There was a problem hiding this comment.
Since this replaces the old maven-deploy-plugin <skip>true</skip>, please double-check that mvn deploy won’t still attempt to deploy the examples module via the default deploy mechanism (i.e., that this actually prevents publishing in the release workflow).
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
1 participant
No description provided.