lukaszlenart opened a new pull request, #293: URL: https://github.com/apache/struts-site/pull/293
## Summary - Deletes `source/maven/`, a one-off snapshot from April 2020 (commit `1e7942f2a`) pinned at **Struts 2.6-SNAPSHOT**. - Each Jekyll publish from `main` copied this stale tree into `output/maven/` on `asf-site`, overwriting the content that the Jenkins JavaDocs job stages there and reverting the displayed version to `2.6-SNAPSHOT`. - The Jenkins job is the sole source of truth for `output/maven/` on `asf-site`, so this directory should not live in `main`. ## Why The `https://struts.apache.org/maven/` site (and its submodule pages such as `/maven/struts2-core/`) showed `Version: 2.6-SNAPSHOT` because of a tug-of-war between two automations: 1. Jenkins JavaDocs job — stages a fresh Maven site (`7.1.2-SNAPSHOT`) into `output/maven/` on `asf-site`. 2. ASF Buildbot Jekyll publish — rebuilds Jekyll from `main` and copies `source/maven/*` into the published output, overwriting the fresh content with the 2020 snapshot. You can see the flip-flop in the `asf-site` log: - `cfd139baf Updates JavaDocs by Jenkins` set `struts2-core/index.html` to `7.0.3` - `bebb08a3e Automatic Site Publish by Buildbot` reverted it to `2.6-SNAPSHOT` Removing `source/maven/` ends the conflict. ## Test plan - [ ] Staging deploy renders correctly (https://struts.staged.apache.org/) — the `/maven/` path should now reflect only what the Jenkins job publishes - [ ] After merge + a Buildbot publish + a Jenkins JavaDocs run, verify https://struts.apache.org/maven/ shows the current version and submodule pages are no longer reverted -- 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]
