Comments on: Tip: Eclipse-BundleShape

By: ignacioalex

ignacioalex — Fri, 28 May 2010 23:07:20 +0000

The Eclipse-BundleShape manifest header is not working for me as well, so I opened the following bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=314962

By: Fraer9

Fraer9 — Mon, 08 Mar 2010 12:48:42 +0000

Hello, i’ve got the same issue. My manifest contains “Eclipse-BundleShape: dir” but when i export the product (plugin based) i have a jar instead of a dir.

I use Eclipse 3.5.2

By: aya

aya — Fri, 21 Aug 2009 22:50:53 +0000

Hy, all!

I set Eclipse-BundleShape: dir in my plug-in and start the Export Product Wizard, but exported RCP Application (plugin based) have JAR with my plug-in instead of waited DIR.

This is a bug?

By: Priyanka

Priyanka — Mon, 17 Aug 2009 20:37:03 +0000

Within my RCP application, i have some resource files like log4j.properties and so on. Our installation is feature based. I do want to pack the plugin except the resource files. The source code and resources are in the same plugin. After installation, all the source code and some resources are in jar. But config files like properties are not. Does Eclipse-BundleShape support this? If not, is there any other way to achieve this.

By: Andrew Niefer

Andrew Niefer — Tue, 27 Jan 2009 00:19:20 +0000

@Eike, it looks like the result in this case is undetermined. While generating scripts, build associates with each bundle a set of feature entry objects representing the elements from the features that include it. This is where the unpack info is coming from. However, it seems that we only actually consult the first entry in the set and don't bother to see what the others say. And we can't predict the order the entries come out of the set. Changes here will be tracked by bug 217005

By: To jar or not to jar (your Eclipse plugin / OSGi bundle) « Codecurl - David Black

Mon, 26 Jan 2009 08:25:16 +0000

[...] By codecurl Categories: Uncategorized That is the question, and it has been answered in Eclipse [...]

By: zx

zx — Thu, 22 Jan 2009 19:54:14 +0000

@eike, I’m not sure what would happen, I’ll consult Andrew Niefer a bit as PDE Build will be making the decision.

By: Eike Stepper

Eike Stepper — Thu, 22 Jan 2009 19:11:27 +0000

Chris, Great! This solution is so obvious that I always wondered why it was not there in the first place. Btw. do you know what would happen with the old feature-based approach, if two contained features express conflicting unpacking desire for the same plug-in?

By: zx

zx — Wed, 21 Jan 2009 22:06:13 +0000

@marco, the feature will always win. If the feature isn’t available or the unpack attribute isn’t specified, the bundle will be consulted for its shape.

@wassim, this isn’t exposed in the UI yet. We haven’t found a good place for it and we haven’t decided to use it in the SDK yet. Currently, there is only validation and code assist to help people.

@ben, heh, I’ve known a few people that have been bitten by that. In general, most of the time you should be packaging your bundles as JARs… it’s better for everyone

By: Ben Vitale

Ben Vitale — Wed, 21 Jan 2009 00:51:56 +0000

Thanks. Digging around to find that ‘.’ behavior was nasty.