[ https://issues.jboss.org/browse/JBIDE-13034?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13034: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you have at least 1 connection in your *OpenShift Explorer* # ASSERT: launch a fresh Eclipse # EXEC: in *OpenShift Explorer*: select your connection # EXEC: pick *Properties* from the context menu of your connection # ASSERT: if your connection has password stored in secure storage, you're prompted to provide the secure storage password. If your connection has no pw stored, you'll get the connection dialog asking you to provide the password. Result: When *Properties view* appears, you'll get a blank dialog on top of Eclipse: !blank-dialog.png! Alternative approach: # ASSERT: make sure you have at least 1 connection in your *OpenShift Explorer* # ASSERT: launch a fresh Eclipse was: # ASSERT: make sure you have at least 1 connection in your *OpenShift Explorer* # ASSERT: launch a fresh Eclipse # EXEC: in *OpenShift Explorer*: select your connection # EXEC: pick *Properties* from the context menu of your connection # ASSERT: if your connection has password stored in secure storage, you're prompted to provide the secure storage password. If your connection has no pw stored, you'll get the connection dialog asking you to provide the password. Result: When *Properties view* appears, you'll get a blank dialog on top of Eclipse: !blank-dialog.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13034?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13034: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you have at least 1 connection in your *OpenShift Explorer* # ASSERT: launch a fresh Eclipse # EXEC: in *OpenShift Explorer*: select your connection # EXEC: pick *Properties* from the context menu of your connection # ASSERT: if your connection has password stored in secure storage, you're prompted to provide the secure storage password. If your connection has no pw stored, you'll get the connection dialog asking you to provide the password. Result: When *Properties view* appears, you'll get a blank dialog on top of Eclipse: !blank-dialog.png! Alternative approach: # ASSERT: make sure you have at least 1 connection in your *OpenShift Explorer* # ASSERT: launch a fresh Eclipse # EXEC: eventually open OpenShift Explorer # EXEC: select your connection # ASSERT: eventually provide your account password or the secure storage password Result: As soon as you provided your pw (account or secure storage), the bland dialog appears. was: # ASSERT: make sure you have at least 1 connection in your *OpenShift Explorer* # ASSERT: launch a fresh Eclipse # EXEC: in *OpenShift Explorer*: select your connection # EXEC: pick *Properties* from the context menu of your connection # ASSERT: if your connection has password stored in secure storage, you're prompted to provide the secure storage password. If your connection has no pw stored, you'll get the connection dialog asking you to provide the password. Result: When *Properties view* appears, you'll get a blank dialog on top of Eclipse: !blank-dialog.png! Alternative approach: # ASSERT: make sure you have at least 1 connection in your *OpenShift Explorer* # ASSERT: launch a fresh Eclipse # EXEC: eventually open OpenShift Explorer # EXEC: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13034?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13034: ------------------------------------------ When asking various users (JBT QE, OpenShift QE, Xavier, etc.) looks like noone beside me is experiencing this so far. Thus Downgrading it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13034?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13034: ------------------------------------------ I tried to reproduce this with a vanilla Juno JEE on Windows 7 and couldn't. I still have no clue what is causing this on my machine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13034?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-13034 at 11/15/12 8:07 AM: -------------------------------------------------------------------- I tried to reproduce this with a vanilla Juno JEE on Windows 7 and couldn't. I still have no clue what is causing this on my machine. Bumping to CR2. was (Author: adietish): I tried to reproduce this with a vanilla Juno JEE on Windows 7 and couldn't. I still have no clue what is causing this on my machine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13034?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13034: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.0.CR2) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13034?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13034: ------------------------------------------ bumped to 4.1.x -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira