Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically release on Maven Central #289

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Automatically release on Maven Central #289

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -238,6 +238,7 @@
<scmpublish.content>${project.reporting.outputDirectory}</scmpublish.content><!-- mono-module doesn't require site:stage for scm-publish -->
<junit5.version>5.9.0</junit5.version>
<checkstyle.version>9.3</checkstyle.version><!-- 10.x requires Java 11 -->
<nexus-staging-maven-plugin.version>1.6.13</nexus-staging-maven-plugin.version>
</properties>

<repositories>
Expand Down Expand Up @@ -476,6 +477,11 @@
<artifactId>maven-surefire-report-plugin</artifactId>
<version>${maven-surefire-report-plugin.version}</version>
</plugin>
<plugin>
<groupId>org.sonatype.plugins</groupId>
<artifactId>nexus-staging-maven-plugin</artifactId>
<version>${nexus-staging-maven-plugin.version}</version>
</plugin>
<!-- Codehaus plugins in alphabetical order -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
Expand Down Expand Up @@ -604,6 +610,16 @@
</execution>
</executions>
</plugin>
<plugin>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if we want to activate it by default or not ?
We can move the configuration to pluginManagement if not and let projects choose to use it explicitly 😇.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe you right ... it will remove vote process at all

another idea to introduce property, eg: autoRelease or something else - default to false
when project want such simple change property value.

one benefit what I see is that repository will be closed after release, now we have two actions: close and release.

for reference: https://www.mojohaus.org/development/performing-a-release.html#Staging_the_Release

<groupId>org.sonatype.plugins</groupId>
<artifactId>nexus-staging-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<serverId>ossrh-staging</serverId>
<nexusUrl>https://oss.sonatype.org/</nexusUrl>
<autoReleaseAfterClose>true</autoReleaseAfterClose>
</configuration>
</plugin>
</plugins>
</build>

Expand Down