| Summary: | No project's feature file should refer to Europa or Ganymede update site | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> |
| Component: | Cross-Project | Assignee: | Oisin Hurley <oisin.hurley> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
David Williams
I believe either a Ganymede or a Europa reference would be 'stop ship', so have marked as 'blocker'. To clarify, these references come from either the "update url" or a "discovery url" inside a feature.xml file. Personally I think a discovery url reference to Ganymede is fine because it allows a user to discover related content from other projects. I know for sure the org.eclipse.sdk feature has a discovery url reference to Ganymede, and it has done this ever since we had a release train update site. I agree no feature should have an "update url" reference to ganymede. Bjorn volunteered, so assigning to him so no one duplicates effort. (And yes, there is one exception to this general rule, and that is that the Platform does provide a "discovery site" of Ganymede). There's no reason for others to do so. This has been remedied in STP 3.4RC4. |