Summary: | get rid of all fragment.properties in core fragments | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Jim des Rivieres <jeem> |
Component: | Resources | Assignee: | DJ Houghton <dj.houghton> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P1 | CC: | Darin_Swanson |
Version: | 2.0 | ||
Target Milestone: | 2.0 F3 | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: |
Description
Jim des Rivieres
2002-05-30 16:10:01 EDT
How is this going to work for the nl fragements which will be produced by RelEng? I presume that the fragment.xml files in them will just have the strings hard- coded in them? The initial blurb is incorrect. Here is a revised body: There is no such thing as a fragment.properties file. fragment.xml files do not have externalized strings. The fragment name and provider name should be included in the fragment.xml. E.g., fragment.xml <fragment id="org.eclipse.foo.win32" name="Foo for Windows" provider-name="Eclipse.org" version="2.0.0" plugin-id="org.eclipse.foo" plugin-version="2.0.0" /> This one slipped through the cracks for build F2. Add to list to consider for next build. We have decided to go with the first approach proposed: put the externalized string into "plugin.properties." Must fix for fix pass 2. *** Bug 18874 has been marked as a duplicate of this bug. *** Fixed. Reviewed. Released. |