This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch deploy
in repository https://gitbox.apache.org/repos/asf/maven-studies.git
The following commit(s) were added to refs/heads/deploy by this push:
new a53372e63 no need for pom.xml update
a53372e63 is described below
commit a53372e6349a374ca7ceca8200174a44381cdba8
Author: Hervé Boutemy <[email protected]>
AuthorDate: Sun Feb 15 10:28:30 2026 +0100
no need for pom.xml update
---
README.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
index 49d600c93..97059706c 100644
--- a/README.md
+++ b/README.md
@@ -23,13 +23,13 @@ Whatever solution is chosen, the fact that Maven Central
Portal now provides an
## Option 1: deploy to file:/target/staging and manual/scripted upload
-Pro: Configuring is easy, then script creating a tar or zip archive and upload
with UI or `curl`.
+Pro: Easy to run (does not even require `pom.xml` configuration), then script
creating a tar or zip archive and upload with UI or `curl`.
-Limitation: scripting for upload (like it or not)
+Limitation: scripting for zip and upload (like it or not)
## Option 2: Sonatype central-publishing-maven-plugin
-Pro: Easy to configure.
+Pro: Easy to configure in `pom.xml`.
Drawbacks:
- no configuration in `pom.xml` `distributionManagement`
