Community
Participate
Working Groups
Created attachment 125932 [details] a list of bundles with their plugin ID. those bundles should not have the property_files folder For instance, the original plugin org.eclipse.jem.util has a bundle emfworkbench.properties, in babel ganymede build, this bundle is under property_files\ folder. The localized bundle hence can not be picked up. The complete list of problematic resource bundles is attached to this defect. In the plugin IDs are seperated with #.
Sounds like a problem with JST/WST.
Reassigning to the component.
X, Yin, can you clarify what is the expected action by us to resolve this problem? If we move the property files from property_files/ directory, where should be there new place?
properties files should not be in property_files folder. for example, instead of org.eclipse.jem.util.nl_fr_3.4.0.v20090201043402.jar property_files\emfworkbench_fr.properties the correct way is to remove the property_files folder org.eclipse.jem.util.nl_fr_3.4.0.v20090201043402.jar emfworkbench_fr.properties
I finally had time to look into this, and here is what is happening: In each of these plugins, there is a property_files folder that is marked as a Java Source folder. Therefore, when the build happens, these property files are moved to the root of the plugin. In the babel version, the translated version remains in a property_files directory, and thus does not match the built version. Now, while it is much less than ideal for WTP to have any property files in the "default package" (the root directory of the plugin), this is certainly not going to change for Ganymede or Galileo. The babel versions should be tweaked to match the build output of our plugins. I am moving this back to babel.
Denis, please check if we can tweak the reg exp to fix that. Thanks!
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
I will close it because this issue was solved by 349107. Thank You.
