Community
Participate
Working Groups
After discussion with my team, concerns over versioning have led us to conclude that we will need a separate update-site for each major stream of wtp. This bug is requesting an addition to the 3.3.0 stream to add a discovery site with an indigo-specific url. Patch coming momentarily.
Targeting. * Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. This is requested by an adopter product. * Is there a work-around? If so, why do you believe the work-around is insufficient? There is no other way to have our update site added to the new server discovery mechanism of a newly downloaded stock wtp / eclipse installation. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? No tests were performed, as our product is still ensuring that the update site is implemented. However, we have determined a hard guarantee that the update site will not need to be changed or moved around and the addresses are permanent and accurate. * Give a brief technical overview. Who has reviewed this fix? The fix adds one line of xml which adds a url to a list of url's. * What is the risk associated with this fix? The risk is near-zero for this patch. In the event the update site does not exist, the servertools UI simply recognizes that hte url does not exist and hides this from the user 100%.
Created attachment 195819 [details] Add an indigo update site to the list of discovery urls
Thanks for filling up the template Rob! that helps to speed up things. Even though the change is one line I still expect testing to ensure that we are loading the new entry, and to ensure that we still load the old entries. I went ahead and did testing of your changes and didn't find a problem.
changes committed to HEAD
changes released to HEAD
New Gerrit change created: https://git.eclipse.org/r/109049
