Comment 1 Glyn Normington 2011-06-13 04:58:14 EDT

It probably makes sense to fix this the next time we upgrade any of the relevant bundles in the EBR.

Comment 2 Chris Frost 2011-06-13 11:36:40 EDT

Also,
http://ebr.springsource.com/repository/app/bundle/version/detail?name=javax.servlet.jsp&version=2.2.0.v201103241009

and should this one still have the com.springsource prefix?

http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.javax.servlet.jsp.jstl&version=1.2.0.v20110517

Comment 3 Violeta Georgieva 2011-06-15 02:39:01 EDT

Hi Glyn,
 
I checked the specification and I think that the bundle is compatible with it [1].

=======
3.11.2 Manifest Localization
"Localized values are stored in property resources within the bundle. The default base name of the bundle localization property files is OSGI-INF/l10n/bundle. The Bundle-Localization manifest header can be used to override the default base name for the localization files. This location is relative to the root of the bundle and bundle fragments. 
...
A localization key can be specified as the value of a bundle's manifest header using the following syntax:
header-value ::= ’%’text
text ::= < any value which is both a valid manifest header value and a valid property key name >
 
For example, consider the following bundle manifest entries:
Bundle-Name: %acme bundle
Bundle-Vendor: %acme corporation
Bundle-Description: %acme description"
=======
 
In our case we have the following headers:
 
Bundle-Vendor: %bundleProvider
Bundle-Localization: plugin
Bundle-Name: %bundleName

Also in the root of the jar file we have plugin.properties file.

My opinion is that EBR should take into consideration the bundle localization properties.

Regards
Vily

[1] http://www.osgi.org/download/r4v43/r4.core.pdf