Community
Participate
Working Groups
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).
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.
.
(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.
