-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b173
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8182254 | 10 | Naoto Sato | P2 | Resolved | Fixed | b12 |
JDK-8181688 | 9.0.4 | Naoto Sato | P2 | Resolved | Fixed | b01 |
JDK 9 defines a mechanism for providing localized resource bundles in more than one single module. For example a library can separate resource bundles for Asian and European languages in two separate modules (say M1 and M2) using service providers. The current naming convention of a ResourceBundleProvider is <bundleName>Provider. Such service type will be in the same package as the resource bundles. Let's say such service type is "p.resources.FooProvider" in module M. "p.resources" will need to be exported to M1 and M2 to implement the providers. The resource bundles are typically in .properties format and its names are p/resources/foo_ja.properties for example. In this case, the resource bundles in M1 and M2 must be renamed to a different package name due to the split package.
This proposes to change the naming convention of the resource bundle service type to a different package "p.resources.spi.FooProvider" such that this will ease the migration especially when M, M1, M2 are defined to different loader in a custom layer where M, M1, M2 can continue to package the resource bundles under p/resources.
This proposes to change the naming convention of the resource bundle service type to a different package "p.resources.spi.FooProvider" such that this will ease the migration especially when M, M1, M2 are defined to different loader in a custom layer where M, M1, M2 can continue to package the resource bundles under p/resources.
- backported by
-
JDK-8181688 Rename <baseName>Provider to <packagename>.spi.<simpleName>Provider
-
- Resolved
-
-
JDK-8182254 Rename <baseName>Provider to <packagename>.spi.<simpleName>Provider
-
- Resolved
-