I am developing a plugin named like xxx.server.openfire.yyy, following the naming convention of a bigger project and using that as root package name for the plugin's classes.
The resource bundle for internationalization was named like the plugin, but was not found since the file had dots in its name and the classloader would look for it in folders that are not there (and won't get packaged by the ant script if you make them).
The solution was to rename the file with underscores xxx_server_openfire_yyy_i18n.properties and apply this patch.
This should not break any other plugin in the source tree. It should be documented on the plugin developer guide.
I am developing a plugin named like xxx.server.openfire.yyy, following the naming convention of a bigger project and using that as root package name for the plugin's classes.
The resource bundle for internationalization was named like the plugin, but was not found since the file had dots in its name and the classloader would look for it in folders that are not there (and won't get packaged by the ant script if you make them).
The solution was to rename the file with underscores xxx_server_openfire_yyy_i18n.properties and apply this patch.
This should not break any other plugin in the source tree.
It should be documented on the plugin developer guide.