You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by kw...@apache.org on 2021/06/02 09:11:20 UTC
[jackrabbit-filevault-package-maven-plugin] 01/02: remove
irrelevant hint on using git-svn
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-package-maven-plugin.git
commit 1242957100acccf9d64902631df6b783009f06e2
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Wed Jun 2 10:42:57 2021 +0200
remove irrelevant hint on using git-svn
---
src/site/markdown/howto_release.md | 3 ---
1 file changed, 3 deletions(-)
diff --git a/src/site/markdown/howto_release.md b/src/site/markdown/howto_release.md
index e0782d1..ae278fa 100644
--- a/src/site/markdown/howto_release.md
+++ b/src/site/markdown/howto_release.md
@@ -47,9 +47,6 @@ Release management tasks
details. Make sure you have added the pgp key information in you maven settings file, especially if you have
more than one key installed locally. See [Appendix B](#B) for the details.
- Releasing the maven artifact works best when operating on the subversion checkout of the project. Using _git svn_
- does not work.
-
1. (optional, prepare your environment. e.g.: `$ export version=1.0.0`)
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 svn (btw: specifying the