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

Bug 71825

Summary: Externalized strings not loaded properly because of manifest files
Product: [Eclipse Project] Platform Reporter: Pratik Shah <ppshah>
Component: RuntimeAssignee: platform-runtime-inbox <platform-runtime-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: eclipse, hudsonr
Version: 1.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Screenshot showing the problem none

Description Pratik Shah CLA 2004-08-11 15:58:50 EDT 
Installing plug-ins from the Eclipse update site, puts a META-INF folder in 
the plug-ins.  This folder has a manifest.mf file with just one line: Manifest-
Version: 1.0.  The externalized Strings of such plug-ins are not loaded from 
the plugin.properties file.  You can see this in the plug-in list of 
the "About Eclipse" dialog.
Comment 1 Pratik Shah CLA 2004-08-11 16:01:31 EDT 
Created attachment 13889 [details]
Screenshot showing the problem

This bug was encountered in the latest 3.0.1 Eclipse build -- M20040811
Comment 2 Pratik Shah CLA 2004-08-11 16:03:09 EDT 
This, however, works fine on 3.0.
Comment 3 Pratik Shah CLA 2004-08-11 16:04:35 EDT 
Re-routing the bug to platform/runtime.
Comment 4 Randy Hudson CLA 2004-08-11 16:09:12 EDT 
Callers of:
Platform#getResourceString(Bundle bundle, String value)
are busted.
Comment 5 Rafael Chaves CLA 2004-08-11 16:11:19 EDT 
I don't know why the MANIFEST.MF is being added, moving to Update to comment on
that.

The problem with loading externalized strings when there is an incomplete JAR
manifest in the plug-in is likely the same as bug 71003 (Pratik, please confirm
that).
Comment 6 Randy Hudson CLA 2004-08-11 16:34:38 EDT 
Rafael, we already have a separate bugzilla open addressing the existence of 
this file.  Bug 71823.

However, the issue to me is that this worked fine in 3.0.0, and is broken in 
3.0.1. Is bug 71003 the same? Was it found on 3.0.0 or 3.0.1?
Comment 7 Rafael Chaves CLA 2004-08-11 16:46:49 EDT 
Bug 71003 was there since 3.0, but bug 71823 (which seems to be post-3.0) has
made it show up more often. Just try adding a simple MANIFEST.MF to any of your
regular plug-ins and it should happen on 3.0 (not for the 1st time you run,
though). I will mark this as duplicate of the Core bug. If you have any good
reasons to believe this is wrong, please reopen.

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