95b5cfd532
* Fixes #5902 - Grab Jetty startup output in documentation. Implemented an Asciidoctor extension that uses `JettyHomeTester` to run Jetty and capture its output. This extension is triggered by the `ServiceLoader` mechanism, so the documentation jar is now in the plugin classpath. Introduced `jetty-halt.xml` so that the JVM can be halted. In this way, Jetty does not produce the "stopping" log lines and therefore they won't be grabbed and included in the documentation. Used the new `include::jetty[]` directive in the documentation. Signed-off-by: Simone Bordet <simone.bordet@gmail.com> Co-authored-by: Greg Wilkins <gregw@webtide.com> |
||
|---|---|---|
| .. | ||
| src | ||
| pom.xml | ||