Community
Participate
Working Groups
Build ID: I20061214-1445 Steps To Reproduce: 1. Create new plugin project using the wizard (the plugin must have at least one class). I have selected it to be standard OSGi bundle, but I think it is valid for the remaining choices. 2. Export the plugin using the Right Click -> Export -> Deployable plugins and features 3. Check the generated plugin, its MANIFEST.MF entry is not the first entry in the zip file. This violates the OSGi spec and creates problems when installing bundles from InputStream. More information: This behaviour may not cause troubles on Equinox implementation (the implementation can simply download the whole file, open it as RandomAccessFile and everything will be correct. However, when the Jar file is opened as stream and the framework tries to get the manifest, it will fail. This is not a problem on Equinox, because it first saves the whole file in its storage and then reads the manifest. However, not all OSGi implementations will have such behaviour and can rely on this part of the OSGi spec.
Danial, would you be able to investigate the creation of a patch? This would happen in the AssembleConfigScriptGenerator class and probably more precisely in the "jaring" target.
*** Bug 136810 has been marked as a duplicate of this bug. ***
In addition to export wizard, PDE generated ANT scripts are also affected from this bug.
I had investigated this and found the place where the fix should go. However, I'm short of time and can't spend enough time for the fix. Once I'm not so occupied I will try to provide a fix.
Created attachment 60131 [details] Proposal fix for this bug Here is a proposal fix for this bug. Please review and post any comment or recommendation.
looks ok to me, we should put this in M7
patch released to HEAD