[jbosstools-issues] [JBoss JIRA] (JBIDE-9923) Once cloning the repo fails because of missing key, you have to add your keys to the prefs and restart eclipse

[ https://issues.jboss.org/browse/JBIDE-9923?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9923 at 10/17/11 4:54 PM: ------------------------------------------------------------------- The root cause is that the key are initialized when the EGit UI plugin is started. The responsible component, the SshSessionFactory is initialized once per eclipse session and not refreshed (even if you change the ssh preferences). @see org.eclipse.egit.ui.Activator#setupSSH @see SshSessionFactory#setInstance @see EclipseSshSessionFactory It should be no problem to fix this since changes in the preferences may be listened to. Tougher parts are most likely integration with EGit since their EclipseSshSessionFactory has a constructor with default access. I guess that we have to provide a fix for EGit here. was (Author: adietish): The root cause is that the key are initialized when the EGit UI plugin is started. The responsible component, the SshSessionFactory is initialized once per eclipse session and not refreshed (even if you change the ssh preferences). @see org.eclipse.egit.ui.Activator#setupSSH @see SshSessionFactory#setInstance @see EclipseSshSessionFactory It should be no problem to fix this since changes in the preferences may be listened to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira