This is an automated email from the ASF dual-hosted git repository.

lukaszlenart pushed a commit to branch feat/WW-5864-struts-maven-plugin-watch
in repository https://gitbox.apache.org/repos/asf/struts.git

commit ea4814954d9947a7042d4a30161c719992bb74a4
Author: Lukasz Lenart <[email protected]>
AuthorDate: Sat Nov 14 09:50:48 2026 +0100

    WW-5864 docs(tools): dev profile to keep struts:watch on locally
    
    Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
 tools/struts-maven-plugin/README.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/tools/struts-maven-plugin/README.md 
b/tools/struts-maven-plugin/README.md
index 4ae083a85..7b52e05cf 100644
--- a/tools/struts-maven-plugin/README.md
+++ b/tools/struts-maven-plugin/README.md
@@ -65,6 +65,24 @@ mvn jetty:run -Dstruts.watch
 
 Without `-Dstruts.watch` a background execution does nothing.
 
+To keep it on while developing, set the property in a profile rather than in 
the pom's top-level `<properties>`.
+Switched on there, every `package`, `install` and CI build would start a 
watcher, and a multi-module build would fail
+the single-module check:
+
+```xml
+<profiles>
+    <profile>
+        <id>dev</id>
+        <properties>
+            <struts.watch>true</struts.watch>
+        </properties>
+    </profile>
+</profiles>
+```
+
+Run `mvn jetty:run -Pdev`, or list `dev` under `<activeProfiles>` in your own 
`~/.m2/settings.xml` so plain
+`mvn jetty:run` watches on your machine while CI never does.
+
 Each push is logged, for example `pushed struts.xml -> 
target/classes/struts.xml`. Files whose output is missing or
 older than the source are pushed once at startup. Filtering follows the 
module's `maven-resources-plugin`
 configuration, including its plugin-level `<filters>`. The pom is read once at 
startup: restart the goal after changing

Reply via email to