[jackrabbit-filevault] branch master updated: trivial: no need to explicitly give profile "apache-release" with release goals

[kw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jackrabbit-filevault.git


The following commit(s) were added to refs/heads/master by this push:
     new 3bbd9e11 trivial: no need to explicitly give profile "apache-release" with release goals
3bbd9e11 is described below

commit 3bbd9e11d1f752a21b8c22e95f6ac5e62ca17613
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Tue Sep 13 13:08:08 2022 +0200

    trivial: no need to explicitly give profile "apache-release" with
    release goals
---
 src/site/markdown/howto_release.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/site/markdown/howto_release.md b/src/site/markdown/howto_release.md
index 96512305..652f339c 100644
--- a/src/site/markdown/howto_release.md
+++ b/src/site/markdown/howto_release.md
@@ -51,7 +51,7 @@ Release management tasks
     2. Execute `mvn clean deploy -Papache-release -Dmaven.deploy.skip=true`. This tests if the release would work.
     3. Execute `mvn release:prepare`. This will update the POM files and tag the release in Git (btw: specifying the
         release version on the commandline doesn't update the module poms anymore lately).
-    4. Execute `mvn release:perform -Papache-release`. This will build the tagged release and deploy the artifacts to
+    4. Execute `mvn release:perform`. This will build the tagged release and deploy the artifacts to
         a new staging repository on _repository.apache.org_. 
         After the build, login to [https://repository.apache.org/][2] and you should see it there.