| Summary: | DS-Check in E4Application is meaningless | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Thomas Schindl <tom.schindl> |
| Component: | UI | Assignee: | Eric Moffatt <emoffatt> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bsd, emoffatt, Lars.Vogel, pwebster, remy.suen |
| Version: | 4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | candidate43 | ||
|
Description
Thomas Schindl
Tom, nice pickup ! Perhaps we should switch over to checking against the EPartService instead (I believe it's contributed through DS isn't it ? I've modified the check to test against the EPartService instead, it is still contributed as a dynamic service... Verified (visually) in I20120312-1730. As per bug 378975, the change made doesn't actually catch the problem as the check now occurs after the call to getDefaultContext(), and so after the attempt to install EModelService into the context fails. Eric please update the milestone to something in the future. I think with Bug 379023 implemented we can remove this check. If the branding plug-in is null this argument is still not set. To test remove the "product" field in the product editor. |