| headless build - problems with tmp folder [message #592319] |
Wed, 25 February 2009 14:56 |
 Chris
Messages: 97
Registered: July 2009 |
Member |
|
|
while executing a headless build the eclipse build process creates several temp files in
${buildDirectory}/tmp. These are used during internal ant tasks like "jarUp, jarIng, ..."
We have like 20 plugins - some relating to each other, some not. They are checked out into
${buildDirectory}/plugins (as expected by the headleass build process).
I have the following problem: Our C.I. server sometimes builds the plugins in parallel
(depending on how many executors are available, and of course the plugins must not relate
to each other).
This leads to the situation, that the first plugin build finishing cleans the tmp
directory, and the other build running in parallel fails.
I think the main problem is to use the same tmp folder for different builds, and to delete
it completely when finishing, thereby killing other builds running in parallel.
I have 2 simple questions (where either of them could solve my problem):
Q1) We are still on Eclipse 3.3 (both for build and runtime environment). Did this
behavior change with Eclipse 3.4 - afaik. I could build 3.3 deliverables with eclipse 3.4.
Q2) Is there a way to specify the "tmp" folder used by the internal ant tasks?
Q3) .... well if !Q1 && !Q2 .... do you have another hint?
Thanks,
Chris
|
|
|
Powered by
FUDForum. Page generated in 0.03256 seconds
] 
Search
Help
Register
Login
Home
