Switch to Sonatype central plugin and disable example publishing#16
Conversation
Release 0.1.0
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.
Switch to Sonatype central plugin and disable publishing for examples
🤖 Augment PR SummarySummary: Updates the examples module’s Maven publishing configuration to use Sonatype’s 🤖 Was this summary useful? React with 👍 or 👎 |
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
| <artifactId>central-publishing-maven-plugin</artifactId> | ||
| <configuration> | ||
| <skip>true</skip> | ||
| <skipPublishing>true</skipPublishing> |
There was a problem hiding this comment.
Since the previous maven-deploy-plugin <skip>true</skip> was removed, mvn deploy may start deploying this module unless central-publishing-maven-plugin is actually active (typically via parent pluginManagement and/or <extensions>true</extensions>). Could you double-check that the examples module is still excluded from publishing in CI/release builds?
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
1 participant
This pull request updates the Maven plugin configuration in the
microsphere-logging-examples/pom.xmlfile to use a more modern publishing plugin and adjusts the configuration key accordingly.Build and publishing configuration:
maven-deploy-pluginwith thecentral-publishing-maven-pluginfromorg.sonatype.centraland updated the configuration to useskipPublishinginstead ofskip. (microsphere-logging-examples/pom.xml)