| Summary: | LaunchUtils#enableActivity has a UI dependency breaking headless launching | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | James Blackburn <jamesblackburn+eclipse> |
| Component: | cdt-debug | Assignee: | cdt-debug-inbox <cdt-debug-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | Ken Ryall <ken.ryall> |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.cortell, pawel.1.piech |
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
|
Description
James Blackburn
There seem to be a whole bunch of new UI dependencies, including status handlers for save before launch, etc. I'll put together a patch. Sigh. I'm a little behind HEAD. I see that in 1.70 ken removed #enableActivity call in the AbstractCLaunchDelegate constructor. Seems like there's no CDT specific change required. (In reply to comment #1) > There seem to be a whole bunch of new UI dependencies, including status > handlers for save before launch, etc. > > I'll put together a patch. James, the launch plugin has had dependency on UI plugins for quite some time, so there are no build-time guards against adding a UI call in a particular part of the plugin. If there was a code path that was UI-free in the past, and we can reasonably keep it that way, then we should try to. But, again, there's no practical/easy way to guarantee those paths remain UI-free going forward other than to refactor the launch plugin into core and ui plugins. (In reply to comment #3) > James, the launch plugin has had dependency on UI plugins for quite some time, I guess before 7 we've been lucky. We could always add the headless launch IApp to CDT if that's of interest to anyone else. |