[jbosstools-issues] [JBoss JIRA] (JBIDE-22079) Import wizard: Error when import a project already existing in workspace

[Jeff MAURY (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff MAURY reassigned JBIDE-22079:
----------------------------------

    Assignee: Jeff MAURY


> Import wizard: Error when import a project already existing in workspace
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-22079
>                 URL: https://issues.jboss.org/browse/JBIDE-22079
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.CR1
>            Reporter: Marián Labuda
>            Assignee: Jeff MAURY
>              Labels: import_wizard, openshift_v3
>             Fix For: 4.4.x
>
>         Attachments: import-error.png
>
>
> When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear).
> Error:
> {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts.
>  One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again.
> An exception stack trace is not available.
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)