| Summary: | Tweak the name of the ECF Target Platform feature | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] ECF | Reporter: | Jeff McAffer <jeffmcaffer> | ||||
| Component: | ecf.releng | Assignee: | Markus Kuppe <bugs.eclipse.org> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | bugs.eclipse.org | ||||
| Version: | 3.2.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Jeff McAffer
For ECF the situation is that we do not make a distinction feature-wise between target components and exemplary UI that can be installed into the SDK. However, until we come up with a better feature separation, IMO it is fine if we rename "Eclipse Communication Framework SDK" into "Eclipse Communication Framework Target Components" and ignore the UI parts. +1 anybody? Released to HEAD Created attachment 169828 [details]
mylyn/context/zip
|