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

Bug 70796

Summary:

[registry] Plugins are not loading strings from properties

Product:

[Eclipse Project] Platform

Reporter:

Chris Rose <offline+eclipsebugs>

Component:

Runtime

Assignee:

platform-runtime-inbox <platform-runtime-inbox>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

major

Priority:

Version:

3.0

Target Milestone:

3.0.1

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
This is a shot of the mis-labeled prefs pages.	none

Description Chris Rose

2004-07-25 17:19:26 EDT

I'm noticing this with two separate plugins:  Log4e and MevenIDE.

The two of them are not properly displaying their menu and preference entries,
instead they are displaying the property name for the relevant strings.

The weird thing is, they both worked just fine initially, failing instead after
adding another plugin.  For example, the Log4e plugin stopped displaying
properly upon installations of the commonsclipse plugin.

Comment 1 Chris Rose

2004-07-25 17:22:35 EDT

Created attachment 13580 [details]
This is a shot of the mis-labeled prefs pages.

Shown here are the prefs entries for log4e and mevenIDE.  As can be seen,
they're not working too well.

Comment 2 Tod Creasey

2004-07-26 09:16:24 EDT

Neither of these are in the Eclipse SDK. Please log to the appropriate tool.

Comment 3 Chris Rose

2004-07-27 21:40:16 EDT

That's all well and good, but how am I supposed to determine which tool is
causing the problem, since it seems to be caused by addition of one to the
other, although this shouldn't happen.

What's more, uninstalling the plugin that triggered the behaviour isn't
reverting the labels to their previous state.  If the problem was in a plugin as
opposed to the platform, why, then, is the change permanent?

Comment 4 Chris Rose

2004-07-27 21:50:32 EDT

More specifically, this bug can be worked around by deleting the
%ECLIPSE_HOME%/configuration directory's contents (although I don't know which
parts are significant) and re-running Eclipse.

Something smells funny here, and I don't think that it's the plugins.

Comment 5 Kim Horne

2004-07-28 08:38:38 EDT

Reassigning to runtime due to configuration directory oddness.

Comment 6 Pascal Rapicault

2004-08-25 09:58:52 EDT

Investigate for 3.0.1

Comment 7 Jim des Rivieres

2004-08-30 11:35:38 EDT

Pascal, Will this be fixed for 3.0.1 RC1?

Comment 8 Pascal Rapicault

2004-08-30 12:05:40 EDT

Are you getting the plugins through an update site, or are you unzipping them in
your eclipse install folder.

Comment 9 Chris Rose

2004-08-30 12:55:13 EDT

Via update sites.  Specifically, MevenIDE and Log4e are the ones that cause the
most hassles, and they're both via update sites.

Comment 10 Pascal Rapicault

2004-08-30 13:30:58 EDT

This seems to have all the characteristics of bug #71003, which has been fixed
in the latest build of 3.0.1.




*** This bug has been marked as a duplicate of 71003 ***