Bundlor: Error parsing bundle manifest header

Error on genereting the MANIFEST.MF . No error message happens only in the eclips error log.

eclipse.buildId=2.3.0.200912171331-RELEASE
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments:  -product com..sts.ide
Command-line arguments:  -os linux -ws gtk -arch x86 -product com..sts.ide

This is a continuation of log file /home/charles/workspace-sts-2.3.0.RELEASE/.metadata/.bak_0.log
Created Time: 2010-01-06 15:43:36.437Error
Fri Jan 08 11:39:10 BRST 2010
Problems occurred when invoking code from plug-in: quot;org.eclipse.core.resourcesquot;.

com..util.osgi.manifest.parse.BundleMa  nifestParseException: Error parsing bundle manifest header []
HP009E:Unexpectedly ran out of data

at com..util.osgi.manifest.parse.standard  .StandardHeaderParser.parsePackageHeader(StandardH  eaderParser.java:67)
at com..util.osgi.manifest.internal.Stand  ardImportPackage.parse(StandardImportPackage.java:  60)
at com..util.osgi.manifest.internal.Compo  undParseable.resetFromParseString(CompoundParseabl  e.java:58)
at com..util.osgi.manifest.internal.Stand  ardBundleManifest.initializeHeaders(StandardBundle  Manifest.java:123)
at com..util.osgi.manifest.internal.Stand  ardBundleManifest.lt;initgt;(StandardBundleManifest.ja  va:78)
at com..util.osgi.manifest.internal.Stand  ardBundleManifest.lt;initgt;(StandardBundleManifest.ja  va:100)
at com..util.osgi.manifest.BundleManifest  Factory.createBundleManifest(BundleManifestFactory  .java:86)
at com..bundlor.util.BundleManifestUtils.  createBundleManifest(BundleManifestUtils.java:58)
at com..bundlor.internal.transformer.Mani  festCreator.create(ManifestCreator.java:94)
at com..bundlor.internal.StandardBundleTr  ansformer.generateManifest(StandardBundleTransform  er.java:120)
at com..server.ide.bundlor.internal.core.  BundlorProjectBuilder.generateManifest(BundlorProj  ectBuilder.java:575)
at com..server.ide.bundlor.internal.core.  BundlorProjectBuilder.build(BundlorProjectBuilder.  java:225)
at com..server.ide.bundlor.internal.core.  BundlorProjectBuilder.build(BundlorProjectBuilder.  java:151)
at org.eclipse.core.internal.events.BuildManager$2.ru  n(BuildManager.java:627)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner  .java:42)
at org.eclipse.core.internal.events.BuildManager.basi  cBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basi  cBuild(BuildManager.java:280)
at org.eclipse.core.internal.events.BuildManager.buil  d(BuildManager.java:361)
at org.eclipse.core.internal.resources.Project$1.run(  Project.java:523)
at org.eclipse.core.internal.resources.Workspace.run(  Workspace.java:1800)
at org.eclipse.core.internal.resources.Workspace.run(  Workspace.java:1782)
at org.eclipse.core.internal.resources.Project.intern  alBuild(Project.java:502)
at org.eclipse.core.internal.resources.Project.build(  Project.java:102)
at com..server.ide.bundlor.ui.BundlorUiPl  ugin$RunBundlorJob.run(BundlorUiPlugin.java:100)
at org.eclipse.core.internal.jobs.Worker.run(Worker.j  ava:55)

Hi,

can you post or attach your template.mf file?

Christian

I put both manifest and template in a zip file.
When I run the quot;update manifestquot; action nothing happens!

charles,

the template.mf in the attached zip seems to be missing a line break at the end of the Import-Package header. When you add this in, does this fix the error?

Christian

Hi Christian,

There is more projects in my workspace with the same error.
Even with the line break the error persists.

The strange part is if I build using bundlor via Maven the manifest.mf is generated.
But within eclipse nothing happens!

Hi all,

Whilst my template.mf file was slightly different, I was also having the same issues within Eclipse\STS.

Here is the snippet that was causing the isssue:

Code:
...
Import-Template: org..*;version=quot;[3.0, 3.1)quot;,
Import-Package: javax.servlet.jsp.jstl.core;version=quot;[1.1.2,1.2.0)quot;,org.eclipse.virgo.web.dm;version=quot;[2.0.0, 3.0.0)quot;,
...
As you can see, there were extra trailing commas for the last item in each list, this appeared to be causing the errors (although the dialog was less than useful).

Hopefully this helps somebody in the future.

Cheers,
Matt

Thanks Matt for such a informative views.