Community
Participate
Working Groups
See forum post http://www.eclipse.org/forums/index.php/t/238154/ When you export a bundle project as a jar file the manifest generated by Bundlor is overwritten with the default which is empty. Steps to reproduce, 1. Download and unzip the attachment and import into Eclipse with the new Virgo Tools installed. 2. Sort out any errors but don't worry about missing dependencies, notice the manifest in /META-INF. 3. Project -> Export as Eclipse RT bundle, you get a warning about a generated manifest, the exported jar is not a valid OSGi bundle.
The tooling has not been released yet, so correcting the version.
See also: http://www.eclipse.org/forums/index.php/t/280053/ I'm going to take at least a look at this one now.
Created attachment 210228 [details] What's up here? OK, this is truly weird. I -- like the second forum poster -- have created a project that is (I think) exactly the same, but the (inaptly named) project testgood doesn't export. Here's the really weird part. The icon on the package in the bad project is different form the one on the project that does export.
Fixed in: http://git.eclipse.org/c/virgo/org.eclipse.virgo.ide.git/commit/?id=5f6018c364768678dff68f4981d6c7feb0eccd7c Cleaned up some exception handling as well.
Oops, not quite. While it worked with my test case, when I went to check Alex's case, it was still broken.
Actually, it was. The problem was that Alwex was using a Java lib I didn't have. When I used my machine's lib it worked fine.