| Summary: | GEF should have its own project update site. | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | David Williams <david_williams> |
| Component: | GEF-Legacy GEF (MVC) | Assignee: | Tom Macdougall <tmacdoug> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | steveshaw |
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
David Williams
This would mean that GEF cannot be discovered unless the client knows the URL to the update site. The default discovery process checks the Eclipse.org update site. (In reply to comment #1) > This would mean that GEF cannot be discovered unless the client knows the URL > to the update site. The default discovery process checks the Eclipse.org > update site. > This is changing in Eclipse 3.2. The Eclipse Platform Feature will include a Callisto update site, which should be the "general" discovery site. The idea is leave the Eclipse Project as the Eclipse Project ... and not the home for everyone else that they happen to agree to include. Plus, besides discovery, the update site is where GEF should put its "fix packs", etc., so that could/should be done independently of sending files to Sonia and Kim! The GEF milestones update site has been made available: http://download.eclipse.org/tools/gef/milestones/update-site Tom - we should create another bugzilla for the release update site... Tom - we should create another bugzilla for the release update site... |