Bug 62881 - JDT/Core could be contributing a content type for JAR manifests
Summary: JDT/Core could be contributing a content type for JAR manifests
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 62924
  Show dependency tree
 
Reported: 2004-05-19 08:02 EDT by Frederic Fusier CLA
Modified: 2004-05-20 17:37 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Fusier CLA 2004-05-19 08:02:28 EDT 
Request from Platform Core:

From bug 62430, it seems JDT/Core could be contributing a content type for JAR
manifests as well. This would spare people from having to set the encoding for
those files "manually". Such a content type definition would look like:

<content-type id="JARManifest" name="%JARManifestName" 
    base-type="org.eclipse.core.runtime.text"
    priority="high"				
    file-names="MANIFEST.MF"
    default-charset="UTF-8"/>

Would you be willing to contribute it?

By the way, tomorrow's integration build will have enhancements regarding
avoiding re-reading files for encoding determination (when we know the file does
not have any useful information in that sense, for instance, a Java file without
a BOM).

Thanks,

Rafael
Comment 1 Frederic Fusier CLA 2004-05-20 08:28:10 EDT 
Fixed.

Changes done in plugin.xml and plugin.properties as requested.
Comment 2 Olivier Thomann CLA 2004-05-20 17:37:54 EDT 
Verified in 200405201600.