Description David Williams 2011-09-23 20:46:09 EDT

As discussed in bug 358415, see especially bug 358415#c7, the current thinking is that features, and Eclipse project repositories, should not have update site URLs. The thinking being that "products" either in the EPP sense, or adopters products, should be the ones deciding what update sites to offer, not each producer of a feature. That leads to clutter. 

We have (if I recall) removed them from all features, except 4: jsdt, xml, jee, and ... ? 

But, I see the logic of not having any, at all. The thinking used to be, "oh, if someone installed only JSDT (or XML) wouldn't it be cool to point them back to the webtools repository". But, at worst, that might conflict some adopters thinking or, at best, might clutter the p2 install UI. For example, EPP JEE Package would surely till want to add .../webtools/... to its list of update sites ... but, ... maybe someone who only re-used the xml editor would not want that ... and consider it "noise". 

There could be implications I am not thinking of, which is why I say "reconsider" :) ... but, I do think it deserves some serious thought for Juno. 

I am putting this in "releng" as a "central" bugzilla component, but, I think, the actual 3 or 4 features with update site URLs are spread out in subprojects, and the changes would have to be made there ... but, hopefully, WTP would have a consistent approach and not vary by sub-project.