slachiewicz opened a new pull request, #147:
URL: https://github.com/apache/maven-archetypes/pull/147

   The site archetypes hand a newly generated project three things that do not 
match the Maven Site Plugin 3.22.0 the same generated POM pins.
   
   **Site descriptor.** All 20 descriptors in the repository were on the v1 
`DECORATION` model, which makes every site build log "You MUST migrate to the 
new model as soon as possible otherwise your build will break in the future". 
Thirteen were a root-element-and-namespace change; the seven under 
`archetype-resources` also needed `<bannerLeft>`/`<bannerRight>` converted from 
child elements to the v2 attribute form. `<name>` maps to `alt` deliberately, 
not to the v2 `name` attribute: Fluido 2.x displays `name` next to the image 
instead of using it as alt text, so mapping it to `name` would have printed the 
raw `${artifactId}` beside the logo.
   
   **Skin.** The generated descriptor pinned Fluido Skin 1.7, a Doxia 1 skin, 
under a Doxia 2 site plugin. Now 2.1.0.
   
   **Locales — the one that actually breaks output.** `maven-archetype-site` 
generated `<locales>en,fr</locales>`. Under Doxia 2 the default locale is the 
root locale and is written `default`; naming `en` puts the English site in 
`en/` and leaves **no `index.html` at the site root**, so a published site 404s 
at its own front page. Now `default,fr`.
   
   `maven-archetype-site`'s own IT asserted `target/site/en` exists, which 
encoded that behaviour; it now asserts the root `index.html` instead.
   
   Verified end to end, not just by schema: all 20 descriptors validate against 
`site-2.1.0.xsd`; `mvn install` including the archetype ITs is green; and 
generating a project from `maven-archetype-site` and running `mvn site` on it 
produces `target/site/index.html` beside `target/site/fr/`, rendered with 
Fluido 2.1.0, with no deprecation warning in the log. Before this change the 
same run produced only `en/` and `fr/`.
   
   *This change was created with AI assistance.*
   


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