Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320930 - Add a Description to the manifest editor
Summary: Add a Description to the manifest editor
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-26 12:39 EDT by Jon Svede CLA
Modified: 2010-07-26 12:53 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 Jon Svede CLA 2010-07-26 12:39:56 EDT 
Build Identifier: 

It would be really handy if the Manifest editor provided a way for the developer to add a description of the project.  In large OSGi/Plug-in/RCP applications this would allow developers browsing the source to read a short description of the function of the plugin/bundle in the case the name isn't descriptive enough.  The description could be be stored in a variety of places: plugin.xml or the manifest itself or perhaps even it's own file.

Reproducible: Didn't try
Comment 1 Curtis Windatt CLA 2010-07-26 12:53:05 EDT 
The options in the manifest editor are based on the entries you can have in an OSGi manifest.  Unless OSGi adds a header (I don't think that there is one currently) to set a description, PDE won't add one to the editor.

There may be circumstances where a detailed description of a bundle is useful, but it is not worth adding a new special Eclipse header.  Closing as WONTFIX.