slachiewicz opened a new issue, #145:
URL: https://github.com/apache/maven-archetypes/issues/145

   A project generated from `maven-archetype-site` builds a site whose 
**English half is empty**. `en/index.html` is the auto-generated *About* report 
rather than the archetype's own index page, and every entry in the English menu 
returns 404. The real content is rendered only under `fr/`.
   
   This is pre-existing and is neither caused nor fixed by #143 or #144.
   
   ### Configuration
   
   `src/main/resources-filtered/archetype-resources/pom.xml` configures:
   
   ```xml
   <plugin>
     <groupId>org.apache.maven.plugins</groupId>
     <artifactId>maven-site-plugin</artifactId>
     <configuration>
       <locales>en,fr</locales>
     </configuration>
   </plugin>
   ```
   
   ### Layout
   
   The archetype ships a **non-localized** `src/site/**` alongside a 
**localized** `src/site/fr/**`, and there is no `src/site/en/`:
   
   ```
   src/site/site.xml            src/site/site_fr.xml
   src/site/apt/                src/site/fr/apt/
   src/site/markdown/           src/site/fr/markdown/
   src/site/xdoc/               src/site/fr/xdoc/
   src/site/fml/                src/site/fr/fml/
   ```
   
   With `en` listed explicitly in `<locales>`, the non-localized `src/site/**` 
is not rendered for it, so only the `fr` tree produces pages.
   
   ### Reproduce
   
   ```
   mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes \
       -DarchetypeArtifactId=maven-archetype-site -DarchetypeVersion=<current>
   cd <generated>
   mvn site
   ```
   
   Then compare `target/site/en/` with `target/site/fr/`: the French tree 
carries the archetype's pages; the English `index.html` is the generated 
*About* report, and the menu entries have no corresponding pages.
   
   ### Impact
   
   This is the archetype whose purpose is to demonstrate Doxia site authoring, 
so the broken half is the first thing most users see. It also means the 
non-localized sources are effectively dead weight — they are shipped into every 
generated project but never rendered.
   
   ### Possible directions
   
   Not proposing a fix, since this is a behaviour change to what generated 
projects produce and that is a maintainer's call. The options appear to be: add 
an explicit `src/site/en/` tree; drop `en` from `<locales>` so the 
non-localized tree serves as the default; or drop the localization from this 
archetype entirely and keep one language.
   
   Happy to prepare whichever is preferred.
   
   Generated-by: Claude Opus 5 (1M context)


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