Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 191774 - [api] Decouple *.context.core and *.monitor.core from using MylarStatusHandler
Summary: [api] Decouple *.context.core and *.monitor.core from using MylarStatusHandler
Status: RESOLVED DUPLICATE of bug 182776
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P1 enhancement (vote)
Target Milestone: 2.0   Edit
Assignee: Mik Kersten CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-08 16:11 EDT by Eugene Kuleshov CLA
Modified: 2007-06-15 20:02 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Kuleshov CLA 2007-06-08 16:11:57 EDT
For standalone use plugins *.context.core and *.monitor.core need to be decoupled from using MylarStatusHandler.

There is also some weird dependency on XmlStringConverter. Because of that single class slim *.context.core plugin requires heavy org.eclipse.mylar plugin with all jars bundled in it. So, it would be nice to move XmlStringConverter into *.context.core
Comment 1 Mik Kersten CLA 2007-06-08 16:33:45 EDT
Yup, we were going to do this as part of bug 182776.  The main driver is that we currently report the org.eclipse.mylyn plug-in as the root of all errors if MylarStatusHandlers is used.  

XmlStringConverter is likely to go into ..mylyn.monitor.core since the monitor needs it and is our top-level thing.  Experimenting now...
Comment 2 Eugene Kuleshov CLA 2007-06-08 16:45:47 EDT
 (In reply to comment #1)
> Yup, we were going to do this as part of bug 182776.

The main point is to use some of those facilities in a "headless" mode, possible without OSGi container.

Moving XmlStringConverter into *.monitor.core would work for me.
Comment 3 Mik Kersten CLA 2007-06-11 18:06:51 EDT
Changing severity since this is not a "major defect" but an enhancement of very high priority.
Comment 4 Mik Kersten CLA 2007-06-11 23:32:35 EDT
Steffen: do you have any constraings on how this is done?  What I think is likely to happen is that we throw more CoreExceptions in order to better integrate with existing Eclipse facilities for exception handling (e.g. bug 182776).
Comment 5 Mik Kersten CLA 2007-06-15 20:02:40 EDT
Mostly done now, rest of this will come from getting rid of MylarStatusHandler entirely on 3.3, bug 182776.

*** This bug has been marked as a duplicate of bug 182776 ***