[ https://issues.jboss.org/browse/JBIDE-21582?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21582: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you have an OpenShift v3 server adapter # EXEC: restart Eclipse Result: You get the connection dialog (if you didnt store the password) or at least the SSL certificate dialog presented right after Eclipse restarted since the server adapter is publishing right away. The actual callstack shows that OpenshiftResourceChangeListener.MagicProjectChangeJob is triggering a publish upon startup: {code} Connection.authorize() line: 232 Connection.connect() line: 205 Connection.retryList(String, OpenShiftException, String) line: 410 Connection.getResources(String, String) line: 365 OpenShiftServerUtils.getService(IServerAttributes, Connection) line: 244 OpenShiftServerUtils.getService(IServerAttributes) line: 233 OpenShiftServerBehaviour.publish(int, List<IModule[]>, IProgressMonitor, IAdaptable) line: 45 Server.publishImpl(int, List<IModule[]>, IAdaptable, IProgressMonitor) line: 3172 Server.publish(int, IProgressMonitor) line: 1330 OpenshiftResourceChangeListener$MagicProjectChangeJob.autoPublish(IResourceChangeEvent) line: 227 OpenshiftResourceChangeListener$MagicProjectChangeJob.run(IProgressMonitor) line: 208 {code} was: # ASSERT: make sure you have an OpenShift v3 server adapter # EXEC: restart Eclipse Result: You get the connection dialog (if you didnt store the password) or at least the SSL certificate dialog presented right after Eclipse restarted since the server adapter is publishing right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)