slachiewicz opened a new pull request, #433: URL: https://github.com/apache/maven-integration-testing/pull/433
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 `master` — `master` 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`](https://github.com/apache/maven/commit/6a1b3e39c2fe48cfde3f96a959106a834d9b4a5f) | | Port the site documentation from APT to Markdown | [`d4b5e85010`](https://github.com/apache/maven/commit/d4b5e850104571580ae7105a20ecf2b5a08bc07b) as amended by [`096d59ec94`](https://github.com/apache/maven/commit/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-based` — `maven-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. <sub>Drafted with Claude — please verify</sub> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
