Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348713 - Missing Bundle-Vendor in generated source bundles
Summary: Missing Bundle-Vendor in generated source bundles
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 348685 348687
  Show dependency tree
 
Reported: 2011-06-08 08:15 EDT by Nicolas Bros CLA
Modified: 2019-02-25 14:41 EST (History)
2 users (show)

See Also:

Attachments
test workspace (510.49 KB, application/x-zip-compressed)
2011-06-08 08:15 EDT, Nicolas Bros CLA 		no flags Details
View All 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 Nicolas Bros CLA 2011-06-08 08:15:14 EDT 
Created attachment 197588 [details]
test workspace

When the Bundle-Vendor entry in the Manifest.MF is externalized to OSGI-INF/I10N/bundle.properties, the corresponding source bundle generated by Buckminster doesn't have any Bundle-Vendor in its Manifest.MF.

Whereas it works if the Bundle-Vendor entry is not externalized, or is externalized using the old mechanism based on a "plugin.properties".

I am attaching a test workspace:
- First, notice that Bundle-Vendor is set in /test/META-INF/MANIFEST.MF
- In the buckminster project, right click on build.cquery and select "Buckminster > Invoke Action... > site.p2", choosing buckminster.properties as the properties file.
- In the build project, open buildFeature_20110608-120609_1.0.0-eclipse.feature/site.p2/plugins/test.source_1.0.0.qualifier.jar
- notice that its Manifest.MF contains no Bundle-Vendor