| Summary: | Make sure to include Mylyn component dependencies to the feature level | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
| Component: | Mylyn | Assignee: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | lmcbout, sebastien.dubois |
| Version: | unspecified | ||
| Target Milestone: | 0.9 | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Alvaro Sanchez-Leon
Mylyn commons core is now at feature level, in addition a work around was introduced to prevent issues during Mylyn re-structuring related to bug 305782 and specifically Bug 366858 The temporary work around is to include a dependency in the R4E feature to the Mylyn feature. Alvaro, I would recommend removing all plug-in level dependencies from the R4E feature. These are redundant and no longer needed since p2 respects all constraints expressed in manifests anyways. The old UM did not do that that is why the tooling still generates these if you compute dependencies. |