I tried and the TP build job failed for some reason. I tried to remove all traces of the special dir targetplatform (jvm arg, shell rm and archive cmd of targetplatform) and the job still tried to use targetplatform. What is worse, my dependant job which builds the product also still wants to use the archived targetplatform from that location
From the build output of the product build:
How can I clean all this? Do I need to delete the jobs and start from scratch to get a clean setup?
EDIT: I might be wrong, I just reconfigured my TP job and checked what it produces in its workspace and everything seems clean. I got confused because I used
targetplatform
as target dir and incidentally this also seems the default name for the archived location
]]>Tomsen 2010-09-06T07:59:12-00:00Re: Changes in a Hudson job config don't show up in the build
https://www.eclipse.org/forums/index.php/mv/msg/174934/557238/#msg_557238
I assume from you used the 'target platform publisher' feature of the
plugin for this? There is a combo box in your job configuration (labeled
'Target Platform') to configure this. Set this combo to the empty entry
if you do not want to use a published target platform.
setpref targetPlatformPath is a persistant setting though, so you will
either have to call setpref targetPlatformPath again with a different
value, or use 'importTargetDefinition -A your.target' to activate
another target platform.
Best regards,
Johannes]]>Johannes Utzig2010-09-06T08:23:19-00:00Re: Changes in a Hudson job config don't show up in the build
https://www.eclipse.org/forums/index.php/mv/msg/174934/557242/#msg_557242
All this works now as expected. Yes, I exported a Target Platform and intend to use it.
I rather have another problem now with the product build step
See post my other post on the svn problems ...
best regards