RE: [pde-dev] Target platform manifest problem.

["Chris Hopkins" <chopkins@xxxxxxx>]

Title: Target platform manifest problem.

 

If there’s any voting associated with these then I second this request? I spent close to an hour the other day repackaging a third party jar into an OSGI jar for our TP. It turned out to be a missing comma in the Export-Package section that caused it to not show up in when the TP was reloaded.

 

  - Chris

 

 

 

 

 

THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended recipient, your use of this message for any purpose is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender so that we may correct our records.

 

---

 

 

From: pde-dev-bounces@xxxxxxxxxxx [mailto:pde-dev-bounces@xxxxxxxxxxx] On Behalf Of Don Laidlaw
Sent: Tuesday, September 08, 2009 1:54 PM
To: Eclipse PDE general developers list.
Subject: [pde-dev] Target platform manifest problem.

 

When creating a target platform from a directory, the target platform will completely ignore any files that have a problem in the manifest. It would be nice to log those and the reason why it happened.

One problem is that if you use Bundle-Symbolicname in the manifest instead of Bundle-SymbolicName, then the target platform completely ignores that bundle. The difference is the capitalization of the “N” in SymbolicName. I believe you should be able to use Bundle-Symbolicname because the OSGi spec says the manifest headers names should be case-insensitive.

Do you consider this a bug? I do.

BTW: you would not believe how long it took to track down this issue :(

--
Best Regards,

Don Laidlaw | Sr. Research Engineer | Infor | office: +1 902-576-5185 | mobile: +1 902-401-6771 | don.laidlaw@xxxxxxxxx