This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch elharo-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-plugin-tools.git
commit bb37ed627d8d8ed506af7536b74d52ad12284091
Author: Elliotte Rusty Harold <elh...@users.noreply.github.com>
AuthorDate: Thu Dec 12 17:40:37 2024 +0000
Fix run-on sentence
---
.../src/site/apt/examples/generate-report.apt.vm | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
a/maven-plugin-report-plugin/src/site/apt/examples/generate-report.apt.vm
b/maven-plugin-report-plugin/src/site/apt/examples/generate-report.apt.vm
index c66afdbd..f090d0f3 100644
--- a/maven-plugin-report-plugin/src/site/apt/examples/generate-report.apt.vm
+++ b/maven-plugin-report-plugin/src/site/apt/examples/generate-report.apt.vm
@@ -59,11 +59,13 @@ Configuring Generation of Documentation Reports
The standard report goal <<<report>>> invokes separate lifecyle of
<<<process-classes>>>.
In a CI environment you now might execute something like <<<mvn clean deploy
site-deploy>>>.
- During <<<site>>> build the standard reports will trigger
<<<process-classes>>> again, depending on your build this may take some time,
because
+ During <<<site>>> build the standard reports will trigger
<<<process-classes>>> again.
+ Depending on your build this may take some time because
stuff like <<<enforcer>>> or generating stubs from a WDSL will be invoked
again, which may lead
to longer build times.
- As of version 3.14.0 a new report goal is defined, <<<report-no-fork>>> which
will not trigger above phase a second time.
+ As of version 3.14.0 a new report goal is defined, <<<report-no-fork>>> which
will not trigger
+ the above phase a second time.
Configure this in your <<<reporting>>> section as follows:
