From 2a0819580cdc31ccc46bfa21d688c55601a12372 Mon Sep 17 00:00:00 2001 From: opencode Date: Fri, 24 Jul 2026 11:33:53 +0000 Subject: [PATCH 1/6] Fix errors, typos, grammar, and broken link in site docs --- src/site/apt/examples/rapid-testing-jetty6-plugin.apt | 2 +- src/site/apt/examples/war-manifest-guide.apt.vm | 2 +- src/site/apt/index.apt.vm | 4 ++-- src/site/apt/overlays.apt.vm | 4 ++-- src/site/apt/usage.apt.vm | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/src/site/apt/examples/rapid-testing-jetty6-plugin.apt b/src/site/apt/examples/rapid-testing-jetty6-plugin.apt index a500a933..c2db3edf 100644 --- a/src/site/apt/examples/rapid-testing-jetty6-plugin.apt +++ b/src/site/apt/examples/rapid-testing-jetty6-plugin.apt @@ -72,4 +72,4 @@ Rapid Testing Using the Jetty Plugin The command will block with Jetty listening on port 8080. - Check the {{{http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin}Jetty Plugin documentation}} for more details. + Check the {{{https://jetty.org/docs/jetty/12/programming-guide/maven-jetty/jetty-maven-plugin.html}Jetty Plugin documentation}} for more details. diff --git a/src/site/apt/examples/war-manifest-guide.apt.vm b/src/site/apt/examples/war-manifest-guide.apt.vm index a3aadb30..fe4e33ab 100644 --- a/src/site/apt/examples/war-manifest-guide.apt.vm +++ b/src/site/apt/examples/war-manifest-guide.apt.vm @@ -66,7 +66,7 @@ WAR Manifest Customization Now, you can control which dependencies are included in <<>> and in the manifest classpath by following these examples. Maven will follow the transitive dependency tree until it gets to artifacts scoped as "provided". - <> No way is shown how to include a dependency in <<>> but not in the manifest classpath. + <> No example is shown for including a dependency in <<>> while excluding it from the manifest classpath. +--------------------+ diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm index 8ebdac0a..d5eec506 100644 --- a/src/site/apt/index.apt.vm +++ b/src/site/apt/index.apt.vm @@ -39,10 +39,10 @@ ${project.name} It builds a WAR file. * {{{./exploded-mojo.html}war:exploded}} is generally used to speed up - testing during the developement phase by creating an exploded webapp + testing during the development phase by creating an exploded webapp in a specified directory. - * {{{./inplace-mojo.html}war:inplace}} another variation of <<>> + * {{{./inplace-mojo.html}war:inplace}} another variation of <<>> where the webapp is instead generated in the web application source directory, which is <<>> by default. diff --git a/src/site/apt/overlays.apt.vm b/src/site/apt/overlays.apt.vm index 741a80e5..969475b7 100644 --- a/src/site/apt/overlays.apt.vm +++ b/src/site/apt/overlays.apt.vm @@ -157,7 +157,7 @@ documentedprojectdependency-1.0-SNAPSHOT.war configure. Default value is: <<>>. * <> - the classifier of the overlay artifact you want to - configure if multiple artifacts matches the groupId/artifactId. + configure if multiple artifacts match the groupId/artifactId. * <> - the files to include. By default, all files are included. @@ -256,7 +256,7 @@ documentedprojectdependency-1.0-SNAPSHOT.war To perform an even more fine grained overwriting policy, overlays can be packaged multiple times with different includes/excludes. For instance if the <<>> file of the - overlay <<>> <> be set in the webapp but other files can be controlled the + overlay <<>> <> be set in the webapp but other files can be controlled in the regular way, define two overlay configurations for <<>>: +-----------------+ diff --git a/src/site/apt/usage.apt.vm b/src/site/apt/usage.apt.vm index 3e3b1cc0..b562e8f5 100644 --- a/src/site/apt/usage.apt.vm +++ b/src/site/apt/usage.apt.vm @@ -129,7 +129,7 @@ documentedproject-1.0-SNAPSHOT.war *Invocation of <<>> goal - To speed up testing during the developement phase, <<>> can be used to generate the WAR in exploded + To speed up testing during the development phase, <<>> can be used to generate the WAR in exploded form. Use the same project as above and invoke: From 2f1534f2dd1acb04e9a01943e01f0c29e4c4890d Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Fri, 24 Jul 2026 11:35:38 +0000 Subject: [PATCH 2/6] Fix typographical error in overlays.apt.vm --- src/site/apt/overlays.apt.vm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/apt/overlays.apt.vm b/src/site/apt/overlays.apt.vm index 969475b7..924c368b 100644 --- a/src/site/apt/overlays.apt.vm +++ b/src/site/apt/overlays.apt.vm @@ -255,7 +255,7 @@ documentedprojectdependency-1.0-SNAPSHOT.war since they have not been configured in the <<<\>>> element. To perform an even more fine grained overwriting policy, overlays can be packaged multiple times - with different includes/excludes. For instance if the <<>> file of the + with different includes/excludes. For example, if the <<>> file of the overlay <<>> <> be set in the webapp but other files can be controlled in the regular way, define two overlay configurations for <<>>: From 5b8caecbb718edd14150b21993368a84e17fb63f Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Fri, 24 Jul 2026 13:51:47 +0000 Subject: [PATCH 3/6] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- src/site/apt/usage.apt.vm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/apt/usage.apt.vm b/src/site/apt/usage.apt.vm index b562e8f5..671bd964 100644 --- a/src/site/apt/usage.apt.vm +++ b/src/site/apt/usage.apt.vm @@ -129,7 +129,7 @@ documentedproject-1.0-SNAPSHOT.war *Invocation of <<>> goal - To speed up testing during the development phase, <<>> can be used to generate the WAR in exploded + To speed up testing during the development phase, <<>> can be used to generate the WAR in exploded form. Use the same project as above and invoke: From 29a658ef3e5f3a87d9d0c5cd298b38ebda980910 Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Fri, 24 Jul 2026 13:52:51 +0000 Subject: [PATCH 4/6] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- src/site/apt/index.apt.vm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm index d5eec506..9599b846 100644 --- a/src/site/apt/index.apt.vm +++ b/src/site/apt/index.apt.vm @@ -42,7 +42,7 @@ ${project.name} testing during the development phase by creating an exploded webapp in a specified directory. - * {{{./inplace-mojo.html}war:inplace}} another variation of <<>> + * {{{./inplace-mojo.html}war:inplace}} is another variation of <<>> where the webapp is instead generated in the web application source directory, which is <<>> by default. From e7281726a2d84876438f745849e60670a375afab Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Fri, 24 Jul 2026 13:54:01 +0000 Subject: [PATCH 5/6] active voice --- src/site/apt/index.apt.vm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm index 9599b846..70a585aa 100644 --- a/src/site/apt/index.apt.vm +++ b/src/site/apt/index.apt.vm @@ -38,7 +38,7 @@ ${project.name} <<>> phase for projects with a packaging type of <<>>. It builds a WAR file. - * {{{./exploded-mojo.html}war:exploded}} is generally used to speed up + * {{{./exploded-mojo.html}war:exploded}} speeds up testing during the development phase by creating an exploded webapp in a specified directory. From 8e10f3e3401d735ae4c96a05cbbb0e51c8c1b763 Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Fri, 24 Jul 2026 13:55:01 +0000 Subject: [PATCH 6/6] Simplify wording for war:exploded goal usage --- src/site/apt/usage.apt.vm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/apt/usage.apt.vm b/src/site/apt/usage.apt.vm index 671bd964..c88c27d4 100644 --- a/src/site/apt/usage.apt.vm +++ b/src/site/apt/usage.apt.vm @@ -129,7 +129,7 @@ documentedproject-1.0-SNAPSHOT.war *Invocation of <<>> goal - To speed up testing during the development phase, <<>> can be used to generate the WAR in exploded + To speed up testing during the development phase, <<>> can generate the WAR in exploded form. Use the same project as above and invoke: