Manage Keys Dialog: new key is not added to the ssh-prefs if a key-file with the same name already exists --------------------------------------------------------------------------------------------------------- Key: JBIDE-8360 URL: https://issues.jboss.org/browse/JBIDE-8360 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.1 Attachments: Screenshot-16.png

Manage Keys Dialog: new key is not added to the ssh-prefs if a key-file with the same name already exists --------------------------------------------------------------------------------------------------------- Key: JBIDE-8360 URL: https://issues.jboss.org/browse/JBIDE-8360 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR2 (tentative) Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.1, 3.3.0.M1 Attachments: Screenshot-16.png Original Estimate: 0 minutes Remaining Estimate: 0 minutes The current behavior is correct IMHO. There's no sense to add a key to the ssh-prefs if the key file is not present on disk. What's not brilliant here is that the user might think that the key was not created since he gets an error. What we could think of is to: * warn instead of displaying an error * OR offer a filename-dialog (allows to provide a valid filename).

Manage Keys Dialog: new key is not added to the ssh-prefs if a key-file with the same name already exists --------------------------------------------------------------------------------------------------------- Key: JBIDE-8360 URL: https://issues.jboss.org/browse/JBIDE-8360 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 3.2.x, 3.3.x Attachments: Screenshot-16.png Original Estimate: 0 minutes Remaining Estimate: 0 minutes The current behavior is correct IMHO. There's no sense to add a key to the ssh-prefs if the key file is not present on disk. What's not brilliant here is that the user might think that the key was not created since he gets an error. What we could think of is to: * warn instead of displaying an error * OR offer a filename-dialog (allows to provide a valid filename).

Manage Keys Dialog: new key is not added to the ssh-prefs if a key-file with the same name already exists --------------------------------------------------------------------------------------------------------- Key: JBIDE-8360 URL: https://issues.jboss.org/browse/JBIDE-8360 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 3.3.x Attachments: Screenshot-16.png Original Estimate: 0 minutes Remaining Estimate: 0 minutes The current behavior is correct IMHO. There's no sense to add a key to the ssh-prefs if the key file is not present on disk. What's not brilliant here is that the user might think that the key was not created since he gets an error. What we could think of is to: * warn instead of displaying an error * OR offer a filename-dialog (allows to provide a valid filename).