Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 376428

Summary: The "postingdirectory" composite site isn't created quite right
Product: [Eclipse Project] Platform Reporter: David Williams <david_williams>
Component: RelengAssignee: David Williams <david_williams>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: P2    
Version: 4.2   
Target Milestone: 4.2 M7   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on:    
Bug Blocks: 355430    
Attachments:
Description Flags
small change to fix? none

Description David Williams CLA 2012-04-10 13:50:38 EDT
In testing if the final to-be-on-downloads composite site was created correctly, I set it to post to .../eclipse4/siteDir/updates

Where is does create (correctly) create a simply update site under 

4.2-I-builds/${buildLabel} 

BUT it updates the composite files directly under /updates, instead of 
/updates/4.2-I-builds

(the composite files directly under /updates would re relatively static, just pointing to the main, "sub" repositories).
Comment 1 David Williams CLA 2012-04-10 18:33:37 EDT
Created attachment 213828 [details]
small change to fix?

Not sure what changed when, but if I'm not mistaken, the composite are just explicitly created one level too high ... perhaps this used to be handled differently, but best to "do right the first time" ... I think. That is, going to make this change and just give it a try rather than analyze deeper.
Comment 2 David Williams CLA 2012-04-10 18:36:21 EDT
.
Comment 3 David Williams CLA 2012-04-10 23:34:39 EDT
(In reply to comment #0)
> (the composite files directly under /updates would re relatively static, just
> pointing to the main, "sub" repositories).

The fix worked, but thought I'd clarify, there is no "composite*" files directly under /updates (on download.eclipse.org, that is) and I see no need for one on build.eclipse.org.