We currently have multiple “language-module.properties” resource with the same path. This prevents from building “fat jar” when you combine all classes/resources together for a standalone program/library.
I.e. it works if you only have one language, but if you rely on two or more “language-module.properties” from multiple languages would be squashed and only one language would be found.
Another question I have is we have an option to “tag only”, at least from command line tools, but this still loads all the xml rules into the system. I wonder if this flag could be pushed into LT class to no load rules if only core functionality is used.