[ https://issues.jboss.org/browse/JBIDE-10581?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-10581: ----------------------------------- Attachment: git2.png -- 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

[ https://issues.jboss.org/browse/JBIDE-10581?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-10581: ----------------------------------- Attachment: git2.png -- 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

[ https://issues.jboss.org/browse/JBIDE-10581?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10581: ------------------------------------------ I have to admit that things are confusing here: IMHO the 2 usecases have to be kept separate: 1) import the OpenShift application to your workspace 2) share an existing project with OpenShift In 1) we clone the OpenShift repo to the given destination. In 2) we create a local repo and push it to remote git repo. In 2) we clone the remote repo (to /tmp) only to get the OpenShift specific configurations and copy them to the preexisting project (in your workspace). We then git share the the preexisting project (create a new git repo in the project folder) and push it to the OpenShift repo. IMHO there are 2 options: 1) We disable the "Destination" text field (since it does not apply to the usecase 2) 2) We use "Repository Location" (instead of "Destination") and use that setting to determine where the git repo for the preexisting project will be created. We are currently reorganizing the OpenShift UI in JBIDE-10528 and we'll have to decide which option (or a different one?) fits best. -- 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

[ https://issues.jboss.org/browse/JBIDE-10581?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10581 at 1/4/12 11:45 AM: ------------------------------------------------------------------- I have to admit that things are confusing here: IMHO the 2 usecases have to be kept separate: 1) import the OpenShift application to your workspace 2) share an existing project with OpenShift In 1) we clone the OpenShift repo to the given destination. In 2) we create a local repo (for the preexisting project) and push it to the remote OpenShift git repo: We clone the remote repo (to /tmp) only to get the OpenShift specific configurations and copy them to the preexisting project (in your workspace). We then create a new git repo (in the project folder), git share the the preexisting project and push it to the OpenShift repo. IMHO there are 2 options: 1) We disable the "Destination" text field (since it does not apply to usecase 2) 2) We use "Repository Location" (instead of "Destination") and use that setting to determine where the git repo for the preexisting project will be created. We are currently reorganizing the OpenShift UI in JBIDE-10528 and we'll have to decide which option (or a different one?) fits best. was (Author: adietish): I have to admit that things are confusing here: IMHO the 2 usecases have to be kept separate: 1) import the OpenShift application to your workspace 2) share an existing project with OpenShift In 1) we clone the OpenShift repo to the given destination. In 2) we create a local repo and push it to remote git repo. In 2) we clone the remote repo (to /tmp) only to get the OpenShift specific configurations and copy them to the preexisting project (in your workspace). We then git share the the preexisting project (create a new git repo in the project folder) and push it to the OpenShift repo. IMHO there are 2 options: 1) We disable the "Destination" text field (since it does not apply to the usecase 2) 2) We use "Repository Location" (instead of "Destination") and use that setting to determine where the git repo for the preexisting project will be created. We are currently reorganizing the OpenShift UI in JBIDE-10528 and we'll have to decide which option (or a different one?) fits best. -- 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

[ https://issues.jboss.org/browse/JBIDE-10581?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-10581. ----------------------------------------- Resolution: Done -- 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

[ https://issues.jboss.org/browse/JBIDE-10581?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10581: ---------------------------------------- Description: The wizard says it will clone the git repo to: but in reality, it is in: was: The wizard says it will clone the git repo to: !git1.png|thumbnail! but in reality, it is in: !git2.png|thumbnail! -- 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