This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 228693 - Manifests have improper plugin name and plugin provider values
Summary: Manifests have improper plugin name and plugin provider values
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Leonard Richardson CLA
QA Contact: Hubert Leung CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-24 11:27 EDT by David Whiteman CLA
Modified: 2012-01-03 13:54 EST (History)
3 users (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 David Whiteman CLA 2008-04-24 11:27:46 EDT 
In bug 219632, the use of improper version strings was addressed.

I see that several of our plugins also have non-standard plugin name and plugin provider values.  The plugin provider should always be Eclipse.org.  The plugin name should probably always have COSMOS as the first word (or at least we should flag any plugins that have single word names such as "pluginName").  This problem is particularly noticeable in the new source plugins that were created for bug 219490.  Can we have a report to flag problems in the name or provider fields, like we do for version strings that don't include the qualifier?
Comment 1 Leonard Richardson CLA 2008-05-29 09:10:30 EDT 
Added the following checks to the build check for plugins:

1) If Bundle-Name does not start with "COSMOS" a warning message is put in the report

2) In the manifest, if Bundle-Vendor is not "Eclipse.org" a warning message is put in the report