Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 295699

Summary:	PDE does not find localization properties file if a fragment provides translations
Product:	[Eclipse Project] PDE	Reporter:	Benjamin Pasero <benjamin_pasero>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	caniszczyk, curtis.windatt.public, hihn, Michael_Rennie
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Benjamin Pasero

2009-11-20 05:36:41 EST

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: I20091030-1201

This happens for me with a setup where I have my plugin.properties file on the same level as plugin.xml while not using the OSGI-INF location (I verified that I dont see this issue with OSGI-INF). My manifest is set to "Bundle-Localization: plugin" but whenever I externalize something from my plugin.xml I get this error decoration. I can reproduce this with 3.5, 3.5.1 and 3.6. 

Is this something others have reported?

Reproducible: Always

Steps to Reproduce:
1. Externalize a String from the plugin.xml using quick fix
2. Ensure that you have plugin.properties on the root of the bundle and not in OSGI-INF location.

Comment 1 Benjamin Pasero

2009-11-20 05:39:46 EST

I should add that the plugin.xml has lots of ther strings that are peferctly fine with regards to being externalized - no error is shown. Its only for new strings I externalize where this happens. Its weird, is there some other location where this info is stored that might be stale?

Comment 2 Benjamin Pasero

2009-11-20 06:42:42 EST

Btw I am using 3.4 and 3.5 for the same project (not the same workspace though) and adding a new string to the plugin.xml from my 3.4 Eclipse does not show this error annotation.

Comment 3 Chris Aniszczyk

2009-11-20 10:05:01 EST

What is your Bundle-Localization value?

That's where we will look for externalized values.

By default, it's the OSGI-INF location as dictated by the OSGi specification when Bundle-Localization isn't specified.

Comment 4 Benjamin Pasero

2009-11-20 10:17:00 EST

Its Bundle-Localization: plugin and I am having a plugin.properties file with all my externalized strings. It works for all of my existing strings, but not for new ones I add :-(

Comment 5 Benjamin Pasero

2009-11-23 04:26:14 EST

Actually the issue seems that I have a fragment in my workspace that sets the plugin as host where I see this error. This fragment contains a plugin_de.properties file (its my I18N fragment). I think I would have found out sooner if the error message was making it clearer why it complains about a missing string.

Comment 6 Curtis Windatt

2012-10-02 15:28:34 EDT

Michael experienced the same issue when he had multiple nl fragments installed from Babel.

PDE grabs all the fragments and adds them to a URL classloader in NLResourceHelper.  However, the host bundle appears to always be added first in the list, so one would think the host location would be checked and used first.

Comment 7 Eclipse Genie

2019-09-18 12:59:17 EDT

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.