[jbosstools-issues] [JBoss JIRA] (JBIDE-12146) Server adapter wizard: does not recognize existing (imported) project it could use for the adapter

[ https://issues.jboss.org/browse/JBIDE-12146?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12146 at 11/22/12 9:22 AM: -------------------------------------------------------------------- I stepped through and found out that when you call {code} EGitUtils.getRemoteURIs(projects[i]) {code} it'll only get the github uri back, the OpenShift uri is missing, your import wizard is therefore not recognizing the project as matching one. The bug has to be in EGitUtils#getRemoteURIs since the project has a remote attached with the correct (and matching) uri: !openshift-remote-uri-present.png! The reason for this is that EGitUtils is getting the remote configuration for "origin" whereas we should tell it to get the remote configuration for the remote that is configured to the project: {code} org.jboss.tools.openshift.RemoteName=openshift {code} EGitUtils is missing this method and I'll add it. In a 2nd step we'd need to change ExpressServerUtils#findProjectsForApplication to pass the configured remote so that EGitUtils that get the right remote. was (Author: adietish): I stepped through and found out that when you call {code} EGitUtils.getRemoteURIs(projects[i]) {code} it'll only get the github uri back, the OpenShift uri is missing, your import wizard is therefore not recognizing the project as matching one. The bug has to be in EGitUtils#getRemoteURIs since the project has a remote attached with the correct (and matching) uri: !openshift-remote-uri-present.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