Community
Participate
Working Groups
Since the main Eclipse Update Manager site (http://download.eclipse.org/updates/3.0/site.xml) only contains Release builds, and the Eclipse Test Update Manager site (http://download.eclipse.org/testUpdates/site.xml) has I and M builds, would it be possible to provide more than one Update URL within a plugin, so that more than one Update URL location can be specified? This would also allow that EMF R 2.0.1 could be on the main Updates site (along with Eclipse, GEF and JDT Previews), but its I and M builds could be on its Secondary Update Manager Site (http://download.eclipse.org/updates/3.0/site.xml). Thus, users who want to update to an I or M release to do so by enabling that checkbox when searching for updates, or to ignore them if they only want R builds. As long as the the URLs have logical names associated with them, it should be fairly intuitive for users which sites to use/search for what types of updates. Note that this functionality is already attainable by misusing the Discovery URL, pointing it at this secondary Update Manager Site - however, I feel that for the sake of preserving the intent of Discovery URLs, this misuse should be removed (this misuse was a temporary "hack" put in place by me pending release of Eclipse 3.0 to its UM site, in order to provide a way for EMF users to use UM to update EMF). However, by removing this hack, we remove access to existing functionality in EMF (UM access to Integration and Maintenance builds). If this feature request can be implemented, then we achieve the best of both worlds. ;-) Thanks, Nick Boldt codeslave@ca.ibm.com
Oops. URL for current EMF Updates is actually http://download.eclipse.org/tools/emf/updates/site.xml, not the one listed above.
Further update. Eclipse ignores Discovery URLs when searching for updates. Thus I was mistaken - you can't "hijack" the Discovery URL to get this functionality; instead, you must manually enter additional URL(s) if you want to get updates from more than one Update location.
The test site is just a test site, and not meant for any development. It is purely used for testing. There have been discussions and we will seriously looking at being able to use the update manager to update from build to build (either M builds or I builds), which will address your second concern. As far as having more than one update site, I doubt that this will get implemented. These decisions have been made before I worked on this component, but there were good reasons to keep it that way. Another way to redirect the updates from a different update site is to set up a site policy (check the online help for instructions).
*** This bug has been marked as a duplicate of 37701 ***
