Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #274837 +++ I think before we can say we have a "good" orbit repo, we need to inject a mirrorURL property for at least the artifact repo (only one use, I believe). I have been unable to figure out a say to do it, other that use a site.xml file. (which I doubt we could do!). Surely it must be part of some ant task? If not, which is easier ... write some Java to read/rewrite the repo with that property? Or just has a little xml script to add it (until is it part of a p2 ant task). Any ideas?
FYI, this need was also documented back in bug 280512. I don't think the info there is signifcant, but will wait to close it as a dup, in case it is. But, let's have main discussion here?
*** Bug 280512 has been marked as a duplicate of this bug. ***
I've retroactively fixed the last 6 "R-builds" and the 2 S-builds (I've learned they are all mirrored). I did not fix existing I builds, but future ones will have the attribute, since the mechanism to add the attribute was added to "promote" automation. (They appear not to be mirrored, but ... having the attribute there won't hurt). To briefly mention "how" this works, in short, we install the WTP Releng tools feature into an instance of Eclipse (currently use Kepler SR1), and use the "addProperties" application as documented in http://wiki.eclipse.org/WTP/Releng/Tools/addRepoProperties The most relevant files in our Orbit (CVS) code repository, in the org.eclipse.orbit.releng.control module, are installEclipseAndTools.sh installEclipseAndTools.xml addRepoProperties.sh
fixed as described
