Skip to content

Port the site documentation from APT to Markdown - #433

Merged
slachiewicz merged 2 commits into
maven-3.10.xfrom
maven-3.10.x-site-markdown
Aug 10, 2026
Merged

Port the site documentation from APT to Markdown#433
slachiewicz merged 2 commits into
maven-3.10.xfrom
maven-3.10.x-site-markdown

Conversation

@slachiewicz

Copy link
Copy Markdown
Member

Back-ports to the live maven-3.10.x line the APT-to-Markdown conversion that is already merged on apache/maven master, where these same five pages live under its/.

Base branch: maven-3.10.x (not mastermaster in this repository is an empty stub since "Branch 3.10.x created", and the IT tree now lives in apache/maven).

Mirrors the master-side conversion

this PR apache/maven master
Rename the site documents ahead of converting them 6a1b3e39c2
Port the site documentation from APT to Markdown d4b5e85010 as amended by 096d59ec94

The five APT sources here are byte-identical to the ones converted on master, so the Markdown is taken over unchanged and the two lines stay in step. Master's fix-up commit (which restored the YAML front matter the port had dropped) is folded into the port commit here rather than replayed as a mistake and its repair.

file now
src/site/apt/index.apt src/site/markdown/index.md
core-it-suite/src/site/apt/index.apt.vm core-it-suite/src/site/markdown/index.md.vm
core-it-suite/src/site/apt/bootstrap.apt.vm core-it-suite/src/site/markdown/bootstrap.md.vm
core-it-support/core-it-plugins/src/site/apt/index.apt.vm .../markdown/index.md.vm
core-it-support/core-it-plugins/maven-it-plugin-core-stubs/src/site/apt/index.apt.vm .../markdown/index.md.vm

The rename is a separate commit so git records it and git log --follow and git blame still reach each page's history — please merge or rebase, not squash.

Verification

apache/maven could not build the four modules under its/, so its commit message records those five pages as converted but unverified. They are verified here, where the modules do build:

  • mvn -N site in each of the four modules that carry a page (., core-it-suite, core-it-support/core-it-plugins, core-it-support/core-it-plugins/maven-it-plugin-core-stubs), on a pristine maven-3.10.x worktree and on this branch, with identical flags. Both green.
  • All 61 generated pages compared: the <title>, <meta name="author"> and <meta name="date"> tags, the visible text and every link target are identical.
  • The toolchain on this branch is maven-site-plugin 3.21.0 / Doxia Site Renderer 2.0.0. The three .md.vm pages keep their .vm suffix and use setext underlines for level two and #[[### ... ]]# for level three, so Velocity cannot swallow a heading as a ## comment. Checked in the output: Running Core ITs Suite, Core ITs Suite Results, Core ITs Suite and Dependencies (incl. Plugins) and Using Local Repository Manager all render, with their anchors unchanged — including #Core_ITs_Suite_and_Dependencies_.28incl._Plugins.29, which bootstrap links to.

The only changes in the HTML are cosmetic: the licence header now appears once as an HTML comment in the body instead of being stripped, and fenced blocks gain class="language-shell".

Two things I did not verify or touch:

  • The full-reactor mvn site fails on this branch, before and after, in maven-it-plugin-ant-basedmaven-enforcer-plugin bans plexus-container-default pulled in transitively by maven-script-ant:2.0.6. Pre-existing and unrelated; that is why the site was built per module.
  • core-it-suite/src/site/markdown/index.md.vm carries github.com/apache/maven-integration-testing/blob/master/... links inherited verbatim from the APT. Some of them no longer resolve now that master is an empty stub. Left alone to keep this a pure format conversion — worth a follow-up.

Drafted with Claude — please verify

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.

Mirrors apache/maven 6a1b3e39c2, which renamed the same five pages under its/ on
master before the tree was moved out of this repository.

Generated-by: Claude Opus 5 (1M context)
Back-port of the conversion already merged on apache/maven master, where these
same five pages live under its/: apache/maven d4b5e85010 as amended by
096d59ec94, which restored the YAML front matter that first commit had dropped.
The APT sources here are byte-identical to the ones converted there, so the
Markdown is taken over unchanged and the two lines stay in step.

- <<<code>>> becomes backticks, <<bold>> becomes **bold**, {{{url}text}}
  becomes [text](url)
- the ASF license header becomes a single block HTML comment
- the APT document header becomes YAML front matter, which has to be the first
  bytes of the file for the parser to see it; it carries the title, author and
  date that the generated page turns into <title> and <meta> tags
- a page that keeps a reference 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
  #[[ ... ]]#

apache/maven could not build the four modules under its/, so the five pages
were merged there converted but unverified. They are verified here: the site of
each of the four modules was built before and after, and the title, author and
date metadata, the visible text and every link target are unchanged.

Generated-by: Claude Opus 5 (1M context)
@slachiewicz slachiewicz added documentation Improvements or additions to documentation maintenance labels Aug 9, 2026
@slachiewicz
slachiewicz marked this pull request as ready for review August 10, 2026 00:29
@slachiewicz
slachiewicz merged commit 69c450f into maven-3.10.x Aug 10, 2026
18 checks passed
@slachiewicz
slachiewicz deleted the maven-3.10.x-site-markdown branch August 10, 2026 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant