This is an automated email from the ASF dual-hosted git repository.
mthmulders pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-release.git
The following commit(s) were added to refs/heads/master by this push:
new 468520a typo: it's
468520a is described below
commit 468520ac8d782d6c5a1419baa554a7ae3542038d
Author: Prasad Gowda <[email protected]>
AuthorDate: Sun Oct 10 02:16:26 2021 +0530
typo: it's
Closes #82
---
maven-release-plugin/src/site/apt/usage.apt.vm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/maven-release-plugin/src/site/apt/usage.apt.vm
b/maven-release-plugin/src/site/apt/usage.apt.vm
index e2384ce..633474a 100644
--- a/maven-release-plugin/src/site/apt/usage.apt.vm
+++ b/maven-release-plugin/src/site/apt/usage.apt.vm
@@ -139,7 +139,7 @@ mvn --batch-mode release:prepare
create release candidates versions using the <<<release:perform>>> goal, but
the final deployed artifact will NOT
be the exact one that has been approved as RCx.
- A common solution is to use a staging repository, where a test-version is
deployed with it's documentation for
+ A common solution is to use a staging repository, where a test-version is
deployed with its documentation for
review. If all is fine, it is then copied to the public repository. Using
this strategy, the artifact that has
been tested IS the one that is deployed.
