[BUG/DESIGN] g11n-java-client - VIP configuration for root application always applies to the shared library, except for product name and version
Open
area/java-client
kind/bug
kind/design
priority/high
- Dominant language
- Java
- Stars
- 72
- Forks
- 69
- Avg merge
- 23h 32m
- Merged PRs (30d)
- 4
Description
Describe the bug
Any shared library that uses the Java client library is forced to use the VIP configurations of the root application (except for product name and version config).
To Reproduce
Steps to reproduce the behavior:
- Use shared library in a root application
- Add configurations for shared library that are different from the root app's config (eg. offlineResourcesBaseUrl, vipServer)
- Notice that only the shared library's productName and version configs are used. The root app's configs are used for the rest.
Expected behavior
In the root application, you should be able to set the shared library's own VIP configurations properly and use it.
For example, the shared library should be able to use its own offlineResourcesBaseUrl config if its l10n files are bundled with the shared library's jar.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.