Community
Participate
Working Groups
In the Eclipse Automotive IDE package, only the following Mylyn plug-ins get installed: * org.eclipse.mylyn.commons.core * org.eclipse.mylyn.commons.notifications.core * org.eclipse.mylyn.commons.notifications.ui * org.eclipse.mylyn.commons.screenshots * org.eclipse.mylyn.commons.ui * org.eclipse.mylyn.commons.workbench When starting it, we get the following warning in the Error Log view: Invalid preference category path: org.eclipse.mylyn.preferencePages.Mylyn (bundle: org.eclipse.mylyn.commons.notifications.ui, page: org.eclipse.mylyn.commons.notifications.preferencePages.Notifications) We suggest to either rework the plug-in dependencies of the org.eclipse.mylyn.commons.notifications.ui such that the contributor of the missing preference category gets pulled in by p2, or to move/reorganize the Mylyn preference categories to avoid this warning.
This log message is caused by the error reporting which pulls-in these bundles (see the related thread on epp-dev). I'm not sure how this can be fixed ATM. Automotive is one of two packages that does not include Mylyn. Thus, you get this log message. Note that there is work in progress moving Mylyn Notifications to the platform. But this is won't happen for Mars SR0.
I think we need to move org.eclipse.mylyn.internal.tasks.ui.preferences.MylynPreferencePage to org.eclipse.mylyn.commons.ui.MylynPreferencePage and change the definition in plugin.xml. Thoughts?
Created attachment 253914 [details] mylyn/context/zip
(In reply to comment #1) > Note that there is work in progress moving Mylyn Notifications to the platform. This is news to me... (In reply to comment #2) > I think we need to move > org.eclipse.mylyn.internal.tasks.ui.preferences.MylynPreferencePage to > org.eclipse.mylyn.commons.ui.MylynPreferencePage and change the definition in > plugin.xml. > > Thoughts? That seems to make sense to me. We could also or instead consider moving the Notifications preference page to the top level since it can be contributed to by any plugin.
(In reply to Sam Davis from comment #4) > (In reply to comment #1) > > Note that there is work in progress moving Mylyn Notifications to the platform. > > This is news to me... I take my knowledge from bug 467038 and referenced bugs/emails. If there was yet no conversation this might happen soon - or not... FWIW, I'm not involved.
Thanks. It doesn't look to me like there is actually any work in progress, yet. AFAIK no Mylyn Commons committer has had any discussions about this in recent years.
I'm not sure what the outcome will be. Frankly, I would expect that this new framework would live in a package namespace of Eclipse Platform UI and thus, requires migration. Anyway, I don't think we should introduce a common Mylyn preference category. Instead, I'd prefer to contribute the Notifications preference page to the "General" category. It's applicable globally. That change should be mentioned in a N&N.
(In reply to Gunnar Wagenknecht from comment #7) > Instead, I'd prefer to contribute the Notifications preference > page to the "General" category. It's applicable globally. +1 (without thinking about which implication this may have for Mylyn users who know where to look)
(In reply to Marcel Bruch from comment #8) > (In reply to Gunnar Wagenknecht from comment #7) > > Instead, I'd prefer to contribute the Notifications preference > > page to the "General" category. It's applicable globally. > > > +1 (without thinking about which implication this may have for Mylyn users > who know where to look) +1 from my side as well - this would actually prepare the UI for intended transfer of Mylyn Notifications to the platform.
create review https://git.eclipse.org/r/#/c/49004/ for the common part and review https://git.eclipse.org/r/#/c/49005/ for the changes in o.e.m.tasks
Thanks Frank. It seems like a good idea to do this for Mars.
The changes have been merged.
