Bugzilla – Full Text Bug Listing
| Summary: | consider linking to Extras update site via the associatedSitesURL mechanism | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> | ||||
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P4 | CC: | ekuleshov, robert.elves | ||||
| Version: | unspecified | Keywords: | helpwanted | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Steffen Pingel
Before we commit to this for 2.0, could someone verify that one of those approaches causes the update site entries to not appear as nodes under the root? More specifically, changes suggested at comment 13 on that bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=166733#c13 I have set this up exactly as suggested but do not see the Extras coming up. All links verified, same syntax used but not verified. It is uploaded to: http://download.eclipse.org/tools/mylyn/update/dev/e3.3/site.xml and the corresponding site XMLs available in: org.eclipse.mylyn-site If someone can point to how I can get this working by experimenting locally we can still consider this for 2.0. Created attachment 72560 [details] screenshot of update manager This is the result when I select the update-site at http://steffenpingel.de/update/ which is setup exactly as pointed it out in comment #2. Each update site is displayed separately. The only quirk I noticed is that the update manager caches the associated repositories so the URL (filename) has to be changed each time the file that stores the associated repositories is changed. Steffen: do you have any clues as to why it is not working for the update site I set up (comment#3)? I may have time to investigate further tomorrow. (In reply to comment #5) > Steffen: do you have any clues as to why it is not working for the update site I > set up (comment#3)? I may have time to investigate further tomorrow. I think the <site> tag is missing the attribute for the url that has the list of linked repositories: <site associateSitesURL="http://download.eclipse.org/.../associateSites.xml">...</site> Steffen, Mik already rolled back stuff in CVS. You can restore those changes from history. Oh, I missed that. I copied revision 1.46 to my update site and I can see in the progress view that the update manager is checking the Mylyn Extras update site. Mik, it is only displayed on the Search Results page (and by default only if updates are available), it never shows up on the Update Sites to Visit page. I can put that line back and review this again once I have both 3.3 and 3.2 builds done. It is sounding like I had the latest extras installed and that's why nothing failed to show up. I would still like to try this but haven't had time. It would be good to do it by early next week so that when people try to update they can see extras if this works out wll enough. Anyone willing to see if they can get it working? (In reply to comment #10) > I would still like to try this but haven't had time. It would be good to do it > by early next week so that when people try to update they can see extras if > this works out wll enough. Anyone willing to see if they can get it working? Mik, what is the setup? Should one just build whole thing using project sets from the wiki pages? By the way, was it intentional that etras site isn't available as a downloadable archive? After installing a bunch of features into a fresh Europa installation I expected the Mylyn update site to appear in the list of "Update sites to visit" like the update sites for WTP, TPTP, EMFT etc. that were automatically added. Is that intentionally not the case? (In reply to comment #12) > After installing a bunch of features into a fresh Europa installation I expected > the Mylyn update site to appear in the list of "Update sites to visit" like the > update sites for WTP, TPTP, EMFT etc. that were automatically added. Is that > intentionally not the case? No, not intentional. Please file a bug and any clues you might have as to why this is the case. (In reply to comment #11) > Mik, what is the setup? Should one just build whole thing using project sets > from the wiki pages? You don't need any setup, just try it on your local filesystem by copying over the site.xml files and experimenting there. Either that or check out mylyn-site. Note that if we do this we might have a maintanance problem because it looks the PDE site.xml editor overwrites the associated sites. > By the way, was it intentional that etras site isn't available as a downloadable > archive? I was was thinking that we wanted to encourage people to get it via update site. In retrospect I can't see much win in leaving this out so adding the download right now. > > After installing a bunch of features into a fresh Europa installation I > expected > > the Mylyn update site to appear in the list of "Update sites to visit" like > the > > update sites for WTP, TPTP, EMFT etc. that were automatically added. Is that > > intentionally not the case? > > No, not intentional. Please file a bug and any clues you might have as to why > this is the case. Opened bug 195057. Bug 195057 is done for the "Extras". Should we still do this? Seems like we should settle on one or the other. If we use an associated site we do not need to contribute the Extras update site (but we should contribute the regular site instead). The associate site gives us more control since we can change it on the server and users only need to have a single update site instead of two. Steffen: the current approach of forcing the linking of the Mylyn Extras site via the Sites to Visit mechanism seems to be the best solution to me, in terms of usability, discoverability, and lack of overhead for the project. My point of view on this is that it is a separate site, with a separate quality bar, so while want it to be easy to access we don't want it to pretend to be the same site. Please post if there are still reasons to do this. I've also added this as a discussion item to today's call. |