Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » default maxParallelMaterializations setting causes java build to fail (Eclipse 3.4 RC3 - headless)
default maxParallelMaterializations setting causes java build to fail (Eclipse 3.4 RC3 - headless) [message #376054] Wed, 11 June 2008 18:21 Go to next message
Claus Klammer is currently offline Claus KlammerFriend
Messages: 17
Registered: July 2009
Junior Member
Hi,
buckminster build from within the workspace worked but when trying to
build the same workspace in headless mode the 'java' build failed almost
every time.
Setting the preference "maxParallelMaterializations=1" solves this issue.

Is this problem caused by buckminster or is the real cause the eclipse
3.4 RC3 platform or jdt?
Maybe the default value should be set to '1' as long as a solution for
this problem can not be provided.
My assumtion is that the problem is caused by the autobuild feature
which is triggerd at a time when not all required components are checked
out (more than one checkout job). This in turn prevents a correct
calculation of the dependency tree. Therefore the build fails with the
message that a dependent component has to be build before.

Cheers,
Claus
Re: default maxParallelMaterializations setting causes java build to fail (Eclipse 3.4 RC3 - headles [message #376057 is a reply to message #376054] Wed, 11 June 2008 23:06 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Claus,
The autobuilds are supposed to be disabled during materialization but
perhaps something has changed in Eclipse that causes failures. I haven't
seen this though.

Can you please enter a bugzilla on this and perhaps provide a little
more info on how the build fails?

Thanks,
Thomas Hallgren

Claus Klammer wrote:
> Hi,
> buckminster build from within the workspace worked but when trying to
> build the same workspace in headless mode the 'java' build failed almost
> every time.
> Setting the preference "maxParallelMaterializations=1" solves this issue.
>
> Is this problem caused by buckminster or is the real cause the eclipse
> 3.4 RC3 platform or jdt?
> Maybe the default value should be set to '1' as long as a solution for
> this problem can not be provided.
> My assumtion is that the problem is caused by the autobuild feature
> which is triggerd at a time when not all required components are checked
> out (more than one checkout job). This in turn prevents a correct
> calculation of the dependency tree. Therefore the build fails with the
> message that a dependent component has to be build before.
>
> Cheers,
> Claus
Re: default maxParallelMaterializations setting causes java build to fail (Eclipse 3.4 RC3 - headles [message #376062 is a reply to message #376057] Thu, 12 June 2008 05:50 Go to previous message
Claus Klammer is currently offline Claus KlammerFriend
Messages: 17
Registered: July 2009
Junior Member
Hi,
I entered a bug description with some additional information on that issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=236796

Thanks for your time,
Claus

Thomas Hallgren schrieb:
> Hi Claus,
> The autobuilds are supposed to be disabled during materialization but
> perhaps something has changed in Eclipse that causes failures. I haven't
> seen this though.
>
> Can you please enter a bugzilla on this and perhaps provide a little
> more info on how the build fails?
>
> Thanks,
> Thomas Hallgren
>
> Claus Klammer wrote:
>> Hi,
>> buckminster build from within the workspace worked but when trying to
>> build the same workspace in headless mode the 'java' build failed
>> almost every time.
>> Setting the preference "maxParallelMaterializations=1" solves this issue.
>>
>> Is this problem caused by buckminster or is the real cause the eclipse
>> 3.4 RC3 platform or jdt?
>> Maybe the default value should be set to '1' as long as a solution for
>> this problem can not be provided.
>> My assumtion is that the problem is caused by the autobuild feature
>> which is triggerd at a time when not all required components are
>> checked out (more than one checkout job). This in turn prevents a
>> correct calculation of the dependency tree. Therefore the build fails
>> with the message that a dependent component has to be build before.
>>
>> Cheers,
>> Claus
Previous Topic:Headless Buckminster for 3.4
Next Topic:Buckminster fails with "Invalid signature file digest for Manifest"
Goto Forum:
  


Current Time: Thu Apr 25 17:13:16 GMT 2024

Powered by FUDForum. Page generated in 0.04922 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top