Bugzilla – Full Text Bug Listing
| Summary: | Have only one EDT feature, or a hierarchy | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Matt Heitz <mheitz> | ||||
| Component: | EDT | Assignee: | Justin Spadea <jspadea> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P1 | CC: | broy2, jqian, jspadea, smythew, svihovec, tdramsey | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Matt Heitz
Created attachment 206467 [details]
Screen shot of Eclipse install panel for EDT features
I agree with doing this, and think we should get it right from the beginning. As part of this, we need to update the name of the "feature group" (think that's the right term). See screen shot and note the name for the parent node is "edt 0.7.0Nxxxxx" -- should be something like "EGL Development Tools (EDT) 0.7.0" so if I'm just a user, I don't need the source code feature right? That's right. We met and came up with the following Feature group: EGL Development Tools (EDT) 0.7.0 (this is currently labeled edt 0.7.0 Nxxxx) Features under this group: EGL Web Developer Tools EGL Web Developer Tools Source Code EGL Web Developer Tools is what we think of as "CE2" or what we are calling the "EDT" feature today. The "SDK" feature should be dropped (for now) from the update site. Will a feature change break the ability for someone to 'check for updates' or easily install a new nightly build? If the answer is yes, we will need to post an update to the forum after making any changes so that users know they will need to do a complete re-install. (In reply to comment #6) > Will a feature change break the ability for someone to 'check for updates' or > easily install a new nightly build? If the answer is yes, we will need to post > an update to the forum after making any changes so that users know they will > need to do a complete re-install. If Check for Updates won't work, is there a way to provide a message when they try (in addition to posting to the forum)? I think a forum post is sufficient. We won't be changing these features all the time. About the update site URL, I assume it's currently set to the nightly build URL? It seems when 0.7 ships, we'll want the update site URL to be set to wherever we expect 1.0 (or 0.8) to be. Done. I'll write up a forum post about the change. If you had the SDK feature installed you should uninstall it since it no longer exists (it won't have updates anymore). It should be replaced by installing the two other features. If you had the other two features installed and not SDK then updates should still work. As for the update site URL, that's not part of site.xml. You enter the URL (nightly, milestone, etc) into the Eclipse install system yourself, and then "find updates" just polls all enabled update sites for new versions of installed features. Should we just name it EGL Development Tools without a version then....that way when folks move from .7 to 1 then they can use the Check for Updates vs putting in a new update site URL. I can see having a different update site for nightly builds though. The label is just a name and has nothing to do with the URL. When 1.0 becomes available, they will see it as an update to 1.0 if we put it at the URL being checked. It looks like you can specify an update site URL in feature.xml (not site.xml), so do we have a URL we think will be the "offical" place we put future released versions like 1.0? Keep in mind anytime the base Eclipse requirement changes then we need to use a new URL so that you can't update to code that doesn't work on your level of Eclipse. It looks like you cannot build the source feature without building the SDK feature. I had simply removed the SDK feature from site.xml so that it wouldn't show up, however if you uncheck "Group items by category" then you see it. I updated its name to match the other names, but my question is: Do we want SDK to display when grouped by category, or leave it visible only when that gets unchecked? has this been resolved now? I think all that's left is what update site URL to specify in feature.xml. This has been finished Closing. |