lukaszlenart opened a new pull request, #314:
URL: https://github.com/apache/struts-site/pull/314

   Follow-up to the javadocs pipeline. The last (green) run published the full 
staged reactor, so module sites landed nested by POM inheritance:
   
   ```
   source/maven/struts2-bom/struts2-parent/struts2-core/dependencies.html
   source/maven/struts2-bom/struts2-parent/struts2-plugins/modules.html
   ```
   
   …but the website menu (`source/_includes/header.html`) links to the flat, 
pre-Struts-7 layout:
   
   | Menu link | Was it resolving? |
   |---|---|
   | `/maven/project-info.html` | ✅ (top-level site) |
   | `/maven/struts2-core/dependencies.html` | ❌ nested |
   | `/maven/struts2-plugins/modules.html` | ❌ nested |
   | `/maven/struts2-core/apidocs/index.html` | ❌ nested |
   
   ## Fix
   Publish only what the menu references, and flatten it:
   - top-level aggregate site (staging root **except** the nested `struts2-bom` 
tree) → `source/maven/`
   - `…/struts2-bom/struts2-parent/struts2-core` → `source/maven/struts2-core`
   - `…/struts2-bom/struts2-parent/struts2-plugins` → 
`source/maven/struts2-plugins`
   
   All four menu links now resolve **with no menu change**. This is safe 
because each module site is self-contained (own `css/js/images`) and 
`struts2-plugins` carries its own submodule sites, so moving whole directories 
keeps their internal links intact. It also drops the unreferenced modules 
(`jakarta`, `apps`, `assembly`) and the `bom`/`parent` scaffolding.
   
   **Trade-off:** secondary "up"/breadcrumb links *inside* the Maven-generated 
pages (e.g. "Parent Project") assumed the deep nesting and may not resolve 
after flattening — the report content, apidocs, and all menu targets do.
   
   Verify with a re-run at `STRUTS_TAG=STRUTS_7_2_1` after merge.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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]

Reply via email to