Community
Participate
Working Groups
http://www.eclipse.org/newsportal/article.php?id=356&group=eclipse.tools.buckminster#356
After some initial though and debugging I'm not so sure anymore this really makes sense. Using the policy file pretty much duplicates what's in the rmap. What I probably need instead is am mechanism to prevent the update manager from resolving "mirrorsURL", "digestURL" and "associateSitesURL" (Bug #238599). Because when I set the rmap to materialize against a local eclipse.org mirror, I don't need the update manager to a) get the list of mirrors and b) maybe even dl from a mirror. On the other hand I suspect Bug #238599 won't be addressed soon. At least not in 3.4 as it might requires API changes (mostly in org.eclipse.update.core.SiteManager unless system properties are acceptable). And working around this issue in Buckminster means cloning a lot of code from org.eclipse.update.core.SiteManager, org.eclipse.update.internal.core.InternalSiteManager, org.eclipse.update.core.model.SiteModelFactory and org.eclipse.update.core.model.DefaultSiteParser (if it is the right location to park the code to ignore the three site.xml attributes).
Closing as WONTFIX since P2 doesn't honor policies either.