Community
Participate
Working Groups
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
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...
(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.
Changing severity since this is not a "major defect" but an enhancement of very high priority.
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).
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 ***