[ https://issues.jboss.org/browse/JBIDE-20740?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20740: ------------------------------------- Well... that was surprisingly challenging to debug ;) It seems it was SUPPOSED to be storing these values in another plugins' preference store (intentionally), but was storing it in its own plugin's preference store. Both plugins' activators were simply named "Activator", and I'd imagine that when some logging was added to the UI, the new import broke the existing code by storing the values in the UI plugin's preferences rather than the "tools" plugin's. Another reason to never name your activator "Activator" ;) As for why it still magically worked on workspace restart, I have absolutely no idea :D I do remember there had previously had the core prefs stored in teh UI plugin, causing a circular dependency, and I had fixed that. But this still worked after that point. I really think the addition of an import is what broke it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)