You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2022/05/06 05:21:44 UTC
[maven-release] branch MRELEASE-955 updated (42fd8c71 -> ed1a0650)
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a change to branch MRELEASE-955
in repository https://gitbox.apache.org/repos/asf/maven-release.git
discard 42fd8c71 [MRELEASE-955] add POM snippet
new ed1a0650 [MRELEASE-955] add POM snippet
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (42fd8c71)
\
N -- N -- N refs/heads/MRELEASE-955 (ed1a0650)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../src/site/apt/examples/{update-versions.apt.vm => update-versions.apt} | 0
maven-release-plugin/src/site/apt/{upgrade.apt => upgrade.apt.vm} | 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename maven-release-plugin/src/site/apt/examples/{update-versions.apt.vm => update-versions.apt} (100%)
rename maven-release-plugin/src/site/apt/{upgrade.apt => upgrade.apt.vm} (100%)
[maven-release] 01/01: [MRELEASE-955] add POM snippet
Posted by hb...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch MRELEASE-955
in repository https://gitbox.apache.org/repos/asf/maven-release.git
commit ed1a065099eabdcba10a04c9966b27a1d0406752
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Fri May 6 07:03:36 2022 +0200
[MRELEASE-955] add POM snippet
---
.../src/site/apt/{upgrade.apt => upgrade.apt.vm} | 40 ++++++++++++++++++++++
1 file changed, 40 insertions(+)
diff --git a/maven-release-plugin/src/site/apt/upgrade.apt b/maven-release-plugin/src/site/apt/upgrade.apt.vm
similarity index 74%
rename from maven-release-plugin/src/site/apt/upgrade.apt
rename to maven-release-plugin/src/site/apt/upgrade.apt.vm
index adbfe070..93f66930 100644
--- a/maven-release-plugin/src/site/apt/upgrade.apt
+++ b/maven-release-plugin/src/site/apt/upgrade.apt.vm
@@ -50,6 +50,46 @@ Upgrading Maven Release Plugin From 2 to 3
{{{https://central.sonatype.org/publish/publish-maven/}the documentation}}
[]
+
+ Then configure <<<maven-release-plugin>>> to use that profile during <<<release:perform>>> with <<<releaseProfiles>>> parameter:
+
++-------+
+<project>
+ [...]
+ <build>
+ [...]
+ <plugins>
+ [...]
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-release-plugin</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+ <releaseProfiles>my-project-release</releaseProfiles>
+ </configuration>
+ </plugin>
+ [...]
+ </plugins>
+ [...]
+ </build>
+
+ [...]
+
+ <profiles>
+ <profile>
+ <id>my-project-release</id>
+ <build>
+ <plugins>
+ [...
+ put here your release-specific plugins invocations, like maven-source-plugin, maven-javadoc-plugin, maven-gpg-plugin, ...
+ ...]
+ </plugins>
+ </build>
+ </profile>
+ [...]
+ </profiles>
+</project>
++-------+
** Short Term: Force Using Maven 3-only Default Release Profile