michael-o commented on issue #1226: URL: https://github.com/apache/maven-site-plugin/issues/1226#issuecomment-3940568830
> > We have several ITs covering your exact case. It boils down to: default,de,fr_CA,ar_SA,pl > > [@michael-o](https://github.com/michael-o) As far as I understand, none of the current `<locales>` configurations seem to cover the use case described in this ticket, where a French site is expected to be generated in the src/site root directory on an English system. > > * `<locales>default</locales>` would generate the site in English. > > * `<locales>fr</locales>` would generate the French site under src/site/fr, not directly in src/site. > > > If I understood the use case that motivated the breaking change in [#1083](https://github.com/apache/maven-site-plugin/issues/1083), it would make it easier to propose a solution that supports both scenarios. > > > [@michael-o](https://github.com/michael-o) Since you introduced the change deliberately in [#1083](https://github.com/apache/maven-site-plugin/issues/1083) what is your opinion? Do we need to change documentation or implementation in this regard? > > [@kwin](https://github.com/kwin) I’d also like to highlight that [#1083](https://github.com/apache/maven-site-plugin/issues/1083) introduced a breaking change that affects existing users without providing any alternative or migration path. Because of that, simply updating the documentation doesn’t seem like a viable long‑term solution. It would be preferable to restore backward compatibility or provide a configurable option so users are not forced into the new behavior. I see, can you please a sample test case for me, I'd like to have a look at it? Our premise was that our root bundles are fixed and contain English content (default) and any other specific locale can overwrite even `en_CA`/`en_US` like catalogue/catalog. -- 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]
