Eclipse Community Forums: Buckminster » bundle build order is taken from feature

Home » Archived » Buckminster » bundle build order is taken from feature

bundle build order is taken from feature [message #494552]

Sat, 31 October 2009 07:21

Eclipse User

Originally posted by: news.eclipse.org.08.lemmster.de

Hi,

it appears that Bucky simply builds bundles in the same order they are
specified in the containing feature. Since the feature order isn't
explicit, this leads to broken builds. How do I make the build
independent of the feature order?

Thanks
Markus

Re: bundle build order is taken from feature [message #494553 is a reply to message #494552]

Sat, 31 October 2009 07:26

Eclipse User

Originally posted by: news.eclipse.org.08.lemmster.de

Markus Kuppe wrote:
> Hi,
>
> it appears that Bucky simply builds bundles in the same order they are
> specified in the containing feature. Since the feature order isn't
> explicit, this leads to broken builds. How do I make the build
> independent of the feature order?

I must add that this only appears to be the case for bundles where the
dependency comes in via import package and not by require bundle. Thus
I've tried to declare a proper dependency by using a buckminster.cspex
[1] without any effect.

Markus

[1]
<cspecExtension>
....
<dependencies>
<dependency name="ch.ethz.iks.slp" componentType="osgi.bundle"/>
</dependencies>
....
</cpsecExtension

Re: bundle build order is taken from feature [message #494560 is a reply to message #494552]

Sat, 31 October 2009 08:32

Eclipse User

Hi Markus,
Buckminster builds bundles in dependency order, leafs first. The order is random if the bundles have no
inter-dependencies and in that case it is fully possible that it defaults to order they are listed in the feature. It
should not become a problem though. The build is in no way dependent on the feature order.

Can you please elaborate what your problem is? Why and where does your build break?

Regards,
Thomas Hallgren

On 10/31/2009 12:21 PM, Markus Kuppe wrote:
> Hi,
>
> it appears that Bucky simply builds bundles in the same order they are
> specified in the containing feature. Since the feature order isn't
> explicit, this leads to broken builds. How do I make the build
> independent of the feature order?
>
> Thanks
> Markus

Re: bundle build order is taken from feature [message #494561 is a reply to message #494553]

Sat, 31 October 2009 08:45

Eclipse User

On 10/31/2009 12:26 PM, Markus Kuppe wrote:
> Markus Kuppe wrote:
> I must add that this only appears to be the case for bundles where the
> dependency comes in via import package and not by require bundle. Thus
> I've tried to declare a proper dependency by using a buckminster.cspex
> [1] without any effect.
>
When you say 'build'. Do you mean 'perform'? The perform command will follow the dependency chain but it will not
consider package imports (they often introduce circular dependencies).

A regular 'build' though, will call on the PDE workspace build. Buckminster will not determine the order of that at all.
So the normal process is:

1. Import (i.e. resolve materialize).
2. Do a full workspace build
3. Perform actions.

Regards,
Thomas Hallgren

Re: bundle build order is taken from feature [message #494567 is a reply to message #494561]

Sat, 31 October 2009 10:19

Eclipse User

Originally posted by: news.eclipse.org.08.lemmster.de

Thomas Hallgren wrote:
> On 10/31/2009 12:26 PM, Markus Kuppe wrote:
>> Markus Kuppe wrote:
>> I must add that this only appears to be the case for bundles where the
>> dependency comes in via import package and not by require bundle. Thus
>> I've tried to declare a proper dependency by using a buckminster.cspex
>> [1] without any effect.
>>
> When you say 'build'. Do you mean 'perform'? The perform command will
> follow the dependency chain but it will not consider package imports
> (they often introduce circular dependencies).
>
> A regular 'build' though, will call on the PDE workspace build.
> Buckminster will not determine the order of that at all. So the normal
> process is:
>
> 1. Import (i.e. resolve materialize).
> 2. Do a full workspace build
> 3. Perform actions.

Hi Thomas,

you can see the full output of the build on our Hudson server [1]. To me
it looks like the workspace build is broken.

Markus

[1] https://ecf2.osuosl.org/hudson/job/C-HEAD-sdk_feature/672/co nsoleFull

Re: bundle build order is taken from feature [message #494690 is a reply to message #494567]

Mon, 02 November 2009 03:35

Eclipse User

Markus Kuppe wrote:
> Thomas Hallgren wrote:
>> Buckminster will not determine the order of that at all. So the normal
>> process is:
>>
>> 1. Import (i.e. resolve materialize).
>> 2. Do a full workspace build
>> 3. Perform actions.
>
> Hi Thomas,
>
> you can see the full output of the build on our Hudson server [1]. To me
> it looks like the workspace build is broken.
>
> Markus
>
> [1] https://ecf2.osuosl.org/hudson/job/C-HEAD-sdk_feature/672/co nsoleFull
Judging from this snipped from the log, I'd say that step #2 is missing:

INFO: Import complete.
Doing full workspace refresh
Waiting for jobs to end
JOB: File Transport Cancel Handler(777) is still running
perform 'org.eclipse.ecf.core#site.p2.zip'

Step #1 completes, and then there's a perform directly after that. Can you please try and add a
build in between?

Regards,
Thomas Hallgren

Previous Topic:	NullPointerException when bundle depends on the system bundle
Next Topic:	Wildcards in provider tag of a .RMAP usin SVN

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 02 11:00:46 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter