On 10/02/2025 13:55, Christopher Schultz wrote:
Assuming we agree that the official releases of Tomcat should have
documentation in English, then I have a further proposal:
+1
- Add "locale" attribute to the <javadoc> tasks in the build with
an explicit locale
+1
For release-managers, I will update the pre-release target to include
javadoc-locale=en_US (or en_GB or just 'en' if we like).
I don't think it matters. Anything that varies (e.g. date format) we
already use an unambiguous form anyway.
In build.properties.default, I will set javadoc-locale to ${user.language}.
I think that is fine since .release takes priority over .default
This should allow anyone downstream to build javadocs in their own
language (either via git clone or pulling the source and removing the
javadoc-locale in build.properties.release) and also users in non-
English default locales to verify a release build.
Now that I've written the above paragraph, it does mean that it's not
trivial for a user to build the javadocs in their own language. I'd love
to hear some suggestions for how to do that with an official source
package. Maybe the "release" target can set the locale somehow. ATM, the
<property> tasks that set up all the properties are outside any target
and apply before any targets get to run, so they cannot be conditional.
We could change that if we want to, though...
build.properties always takes priority so they just need to set a locale
in there.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
