This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new b6325d5c [MNGSITE-446] Properties file gets deleted by default. (#653)
b6325d5c is described below
commit b6325d5cb8060a887ad01bb2d9bca02d8f4c86a6
Author: Matthias Bünger <buk...@users.noreply.github.com>
AuthorDate: Wed Jan 29 22:49:55 2025 +0100
[MNGSITE-446] Properties file gets deleted by default. (#653)
* [MNGSITE-446] Properties file gets deleted by default.
* Feedback
* Change to active
---
content/apt/guides/mini/guide-releasing.apt | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/content/apt/guides/mini/guide-releasing.apt
b/content/apt/guides/mini/guide-releasing.apt
index b2961fa1..04bd5287 100644
--- a/content/apt/guides/mini/guide-releasing.apt
+++ b/content/apt/guides/mini/guide-releasing.apt
@@ -235,12 +235,11 @@ checkpoint.prepared-release=OK
checkpoint.check-in-development-version=OK
-----
- The <release.properties> file is created while preparing the release. After
performing the release the file remains within the project root
- directory until the maven user deletes it. The <release.properties> file
can be given to any developer within the team and
- by simply excuting the <<<release:perform>>> goal can create and deploy a
new instance of the project artifact time and again.
+ The <release.properties> file is created while preparing the release.
+ By default the file gets deleted after a successful release.
- During the execution of the <<<release:perform>>> goal the entire maven
build lifecycle is executed on the project.
- The tagged project source code is extracted, compiled, tested, documented
and deployed. An instance of the release artifact is deployed
+ During the execution of the <<<release:perform>>> goal, Maven executes the
project's entire build lifecycle.
+ The tagged project source code is extracted, compiled, tested, documented,
and deployed. An instance of the release artifact is deployed
to the machine's local repository. An another instance of the release can
be deployed to a remote repository by configuring the
<distributionManagement> element within the <pom.xml> file.
