Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 323163

Summary: Properties in MANIFEST affect naming of bundles
Product: z_Archived Reporter: rzillmann
Component: BuckminsterAssignee: buckminster.core-inbox <buckminster.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: thomas
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description rzillmann CLA 2010-08-19 11:37:23 EDT
Build Identifier: M20100211-1343

Hi, 
I want to create an OSGi-bundle jar with the help of buckminster. When I normally invoke the "bundle.jar" action after resolving a query, I got a jar-file named like "Bundle-SymbolicName_Bundle-Version". The values of this properties were taken from the MANIFEST.MF file inside the OSGi bundle. 
But now I have the following problem. Because of some other functionality I enhanced the MANIFEST file with some properties, one of them is named like "Something-Bundle-Version" with an acording value. If I invoke the "bundle.jar" action at a bundle with such a property inside the MANIFEST, I get a final bundle with the naming structure: "#Bundle-SymbolicName#_#Bundle-Version#Something-#Value.of.Something-Bundle-Version#.jar" (The # signs are not in the name of the bundle, these are just to clarify the names).
I suppose that Buckminster parses the MANIFEST file in a curious manner and have problems, when there are the string "Bundle-Version" more than one time available (although every property is unique).
Perhaps there is a way to bypass that problem, but I didn't find it. 

Reproducible: Always

Steps to Reproduce:
1. Enhance the MANIFEST file of an OSGi bundle with a property included "Bundle-Version"
2. query and resolve that OSGi Bundle
3. perform "bundle.jar"
Comment 1 Thomas Hallgren CLA 2010-08-19 17:11:53 EDT
Buckminster doesn't parse the Manifest. We leave that part to the Equinox framework.

What happens if you try and export the bundle from your IDE using the standard menu choice for PDE export?
Comment 2 Thomas Hallgren CLA 2011-03-31 12:02:40 EDT
This was caused by a missing anchor in a regexp in our contributed build.xml. It's fixed in trunk, rev 11763