Eclipse Community Forums: Buckminster » Binary projects result in nested jars with PDE build

Home » Archived » Buckminster » Binary projects result in nested jars with PDE build

Binary projects result in nested jars with PDE build [message #378527]

Tue, 15 July 2008 05:14

Eclipse User

Hi,

we use BM to materialize bundles into the workspace where they're added
as binary projects. This works fine up to the moment where we feed this
workspace to PDE build to create our product. All binary projects end up
being "normally" packaged by PDE which results in the original jars
nested in newly created jars. Obviously this causes problems at runtime
(RCP doesn't even start).

ATM I see two solutions:

- Do not materialize into the workspace but e.g. site mirror instead.
The site mirror is feed to PDE build via baseLocation and/or pluginPath.
Unfortunately this doesn't work well since not all our bundles originate
from an update site and BM currently doesn't support rules like site
mirror binary projects but materialize source projects to workspace.

- Tell PDE build to not repackage binary projects but simply consume the
original binary bundle. But can a binary project be distinguished from a
source project? To me it seems the only indicator is a nested jar with
the same name as the project.

Any hints are greatly appreciated.

Cheers
Markus

P.S. The reason we don't use BM's product export is because is doesn't
support building for several platforms simultaneously (yet?).

Re: Binary projects result in nested jars with PDE build [message #378531 is a reply to message #378527]

Tue, 15 July 2008 06:40

Eclipse User

Hi Markus,

Markus Alexander Kuppe wrote:
> Hi,
>
> we use BM to materialize bundles into the workspace where they're added
> as binary projects. This works fine up to the moment where we feed this
> workspace to PDE build to create our product. All binary projects end up
> being "normally" packaged by PDE which results in the original jars
> nested in newly created jars. Obviously this causes problems at runtime
> (RCP doesn't even start).
>
> ATM I see two solutions:
>
> - Do not materialize into the workspace but e.g. site mirror instead.
> The site mirror is feed to PDE build via baseLocation and/or pluginPath.
> Unfortunately this doesn't work well since not all our bundles originate
> from an update site and BM currently doesn't support rules like site
> mirror binary projects but materialize source projects to workspace.
>
Not sure what you mean here. You can always create mspec-nodes for the
binary projects that will redirect them into your target platform if you
like. That should work with both the site.mirror and eclipse.import
reader types.

> - Tell PDE build to not repackage binary projects but simply consume the
> original binary bundle. But can a binary project be distinguished from a
> source project? To me it seems the only indicator is a nested jar with
> the same name as the project.
>
Buckminster had a bug similar to this a while back but we fixed it so
that the original jars are used in the build. So using the Buckminster
product export would solve this.

> Any hints are greatly appreciated.
>
> Cheers
> Markus
>
> P.S. The reason we don't use BM's product export is because is doesn't
> support building for several platforms simultaneously (yet?).

Not the way you want it I guess. We support platform agnostic builds but
if you want several builds, one for each platform, then you need to
spawn a new buckminster build (with a new output folder) for each platform.

Suggestions on how to improve this are of course very welcome.

Regards,
Thomas Hallgren

Re: Binary projects result in nested jars with PDE build [message #378533 is a reply to message #378531]

Tue, 15 July 2008 07:01

Eclipse User

Thomas Hallgren wrote:
>> - Do not materialize into the workspace but e.g. site mirror instead.
>> The site mirror is feed to PDE build via baseLocation and/or pluginPath.
>> Unfortunately this doesn't work well since not all our bundles
>> originate from an update site and BM currently doesn't support rules
>> like site mirror binary projects but materialize source projects to
>> workspace.
>>
> Not sure what you mean here. You can always create mspec-nodes for the
> binary projects that will redirect them into your target platform if you
> like. That should work with both the site.mirror and eclipse.import
> reader types.

But doesn't this mean that I have to maintain the mspecs when I add a
new binary bundle?

>> - Tell PDE build to not repackage binary projects but simply consume
>> the original binary bundle. But can a binary project be distinguished
>> from a source project? To me it seems the only indicator is a nested
>> jar with the same name as the project.
>>
> Buckminster had a bug similar to this a while back but we fixed it so
> that the original jars are used in the build. So using the Buckminster
> product export would solve this.

Yep, Buckminster handles this scenario perfectly. :) Do you happen to
remember the bug. Might be worth to file a similar bug against PDE build.

>> P.S. The reason we don't use BM's product export is because is doesn't
>> support building for several platforms simultaneously (yet?).
>
> Not the way you want it I guess. We support platform agnostic builds but
> if you want several builds, one for each platform, then you need to
> spawn a new buckminster build (with a new output folder) for each platform.
>
> Suggestions on how to improve this are of course very welcome.

I'd rather not compile all bundles for each platform over and over
again, just to avoid inconsistencies between the platform builds.

Cheers
Markus

Re: Binary projects result in nested jars with PDE build [message #378535 is a reply to message #378533]

Tue, 15 July 2008 08:06

Eclipse User

Markus Alexander Kuppe wrote:
>>> - Tell PDE build to not repackage binary projects but simply consume
>>> the original binary bundle. But can a binary project be distinguished
>>> from a source project? To me it seems the only indicator is a nested
>>> jar with the same name as the project.
>>>
>> Buckminster had a bug similar to this a while back but we fixed it so
>> that the original jars are used in the build. So using the Buckminster
>> product export would solve this.
>
> Yep, Buckminster handles this scenario perfectly. :) Do you happen to
> remember the bug. Might be worth to file a similar bug against PDE build.

Never mind, https://bugs.eclipse.org/bugs/show_bug.cgi?id=212411

Re: Binary projects result in nested jars with PDE build [message #378540 is a reply to message #378533]

Tue, 15 July 2008 08:58

Eclipse User

Markus Alexander Kuppe wrote:
> Do you happen to
> remember the bug. Might be worth to file a similar bug against PDE build.

https://bugs.eclipse.org/240821

Previous Topic:	'No component match was found' error - Resolve to Wizard
Next Topic:	Product export doesn't run custom build hooks

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 08 18:11:19 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter