From 9f69eb7743c727da309a9033ec9ad27af86d87bd Mon Sep 17 00:00:00 2001
From: Abdullah <89297042+AzazelSensei@users.noreply.github.com>
Date: Fri, 14 Aug 2026 20:12:17 +0300
Subject: [PATCH] Clarify deploy without editing this projects POM

distributionManagement can come from a parent, or from
-DaltDeploymentRepository on the command line.

Closes #200
---
 src/site/markdown/usage.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/site/markdown/usage.md b/src/site/markdown/usage.md
index fd5b8f1..00bf6c9 100644
--- a/src/site/markdown/usage.md
+++ b/src/site/markdown/usage.md
@@ -35,7 +35,9 @@ The Deploy Plugin has two basic functions. In most project builds, the `deploy`
 
 In most cases, this mojo is invoked when you call the `deploy` phase of the default build lifecycle.
 
-To enable this mojo to function, you must include a valid `<distributionManagement/>` section POM, which at the minimum provides a `<repository/>` defining the remote repository location for your artifact. To separate snapshot artifacts from release artifacts, you can also specify a `<snapshotRepository/>` location. Finally, to deploy a project website, you must specify a `<site/>` section here as well. It&apos;s also important to note that this section can be inherited, allowing you to specify the deployment location one time for a set of related projects.
+To enable this mojo to function, you must provide a remote repository location. The usual way is a `<distributionManagement/>` section in the POM, which at the minimum provides a `<repository/>`. To separate snapshot artifacts from release artifacts, you can also specify a `<snapshotRepository/>` location. Finally, to deploy a project website, you must specify a `<site/>` section here as well. It&apos;s also important to note that this section can be inherited, so you do not have to repeat it in every module.
+
+You do not have to edit this project&apos;s POM if the location already comes from a parent, or if you pass `-DaltDeploymentRepository=id::url` (and the matching snapshot / other artifact variants) on the command line. The `id` still has to match a `<server/>` entry in `settings.xml` when the repository needs authentication.
 
 If your repository is secured, you may also want to configure your `settings.xml` file to define corresponding `<server/>` entries which provides authentication information. Server entries are matched to the different parts of the distributionManagement using their `<id/>` elements. For example, your project may have a distributionManagement section similar to the following: