From 29c1e6c045e604930c80bb79b474e6327931e950 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Thu, 6 Aug 2026 19:44:54 +0200 Subject: [PATCH 1/2] Rename the site documents ahead of converting them A pure rename, so that git records it and `git log --follow` and `git blame` still reach the history of each page after the conversion that follows. The content is still APT at this point and the site does not build between the two commits. --- src/site/{apt/usage.apt.vm => markdown/usage.md.vm} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename src/site/{apt/usage.apt.vm => markdown/usage.md.vm} (100%) diff --git a/src/site/apt/usage.apt.vm b/src/site/markdown/usage.md.vm similarity index 100% rename from src/site/apt/usage.apt.vm rename to src/site/markdown/usage.md.vm From b3a2e1636f5fb5c7e9b52f5036845606a286ffe8 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Thu, 6 Aug 2026 19:44:54 +0200 Subject: [PATCH 2/2] Port the usage page from APT to Markdown Converted with doxia-converter and then cleaned up by hand: - <<>> becomes backticks, <> becomes **bold**, {{{url}text}} becomes [text](url) - the ASF license header becomes a single block HTML comment - the page keeps a Velocity reference, so it stays a .vm. Velocity reads ## as a line comment and would silently swallow every ATX heading below level one, so subsections use setext underlines and anything deeper is wrapped in #[[ ... ]]# Verified by building the site before and after: the rendered page is unchanged apart from / becoming / and quotes in prose picking up the Markdown module's typographic substitution. --- src/site/markdown/usage.md.vm | 76 ++++++++++++++--------------------- 1 file changed, 31 insertions(+), 45 deletions(-) diff --git a/src/site/markdown/usage.md.vm b/src/site/markdown/usage.md.vm index e038356e6..14862532e 100644 --- a/src/site/markdown/usage.md.vm +++ b/src/site/markdown/usage.md.vm @@ -1,60 +1,47 @@ - ------ - Usage - ------ - Edwin Punzalan - ------ - 2006-07-05 - ------ + -Usage +# Usage -* Compiling Your Java Sources +Compiling Your Java Sources +--------------------------- - The goals for the Compiler Plugin are bound to their respective phases in the - build lifecycle. So to compile your sources, you need only to tell maven - until which lifecycle to execute. The following will compile your sources: +The goals for the Compiler Plugin are bound to their respective phases in the build lifecycle. So to compile your sources, you need only to tell maven until which lifecycle to execute. The following will compile your sources: -+----- +```unknown mvn compile -+----- +``` - To compile your test sources, you'll do: +To compile your test sources, you'll do: -+----- +```unknown mvn test-compile -+----- +``` - The above command will execute both <<>> and - <<>> since the <<>> phase happens a few phases - before the <<>> phase. +The above command will execute both `compiler:compile` and `compiler:testCompile` since the `compile` phase happens a few phases before the `test-compile` phase. -* Configuring Your Compiler Plugin +Configuring Your Compiler Plugin +-------------------------------- - Since the Compiler Plugin executes automatically during their phases, you - don't have to put <<>> unlike many other plugins. However, you - should specify the version of the Compiler Plugin. +Since the Compiler Plugin executes automatically during their phases, you don't have to put `executions` unlike many other plugins. However, you should specify the version of the Compiler Plugin. -+----- +```unknown ... @@ -73,5 +60,4 @@ mvn test-compile ... -+----- - +```