7.0.X, 7.1.X, Master
Due to com.liferay.lang.merger plugin we do copy Language*.properties file from the language module to the module that requires them. For example it happens with com.liferay.staging.processes.web and com.liferay.staging.lang modules.
So that when a com.liferay.staging.lang key needs to be overriden often the user interprets that they need to override the ResourceBundleLoader from that module, but that doesn't always work if we're employing the key from the com.liferay.staging.processes.web using the calling class (or classloader) to retrieve the ResourceBundleLoader. We should not couple the module key overwrite to our build process.
Steps to Reproduce:
- Use https://dev.liferay.com/en/develop/tutorials/-/knowledge_base/7-0/overriding-language-keys to override the publish-templates key. As bundle.symbolic.name use com.liferay.staging.lang where the key is in the source code.
- Deploy the created module.
The key should be overridden in the staging publishing page.
The key isn't overridden.
The actual way to override the keys isn't very intuitive, and it requires that if a common key needs to be overriden it must be done for every module explicitly.
LPS-106976 Do not use -includeresource: content= to add Language.properties files