Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-22079

Import wizard: Error when import a project already existing in workspace

    Details

    • Sprint:
      devex #117 July 2016
    • Story Points:
      8
    • Steps to Reproduce:
      Hide

      ASSERT: Have a project (jboss-kitchensink from EAP template) in workspace.
      EXEC: Create a new application using jboss eap template and kitchensink project (CONTEXT_DIR param is equal to kitchensink)
      ASSERT: In Import wizard user is asked to provide alternative git repo if it already exists or reuse the existing one. You can choose different git clone location or reuse the one (it does not matter).
      EXEC: Finish the import wizard.

      RESULT: Application is trying to import a project to workspace but it fails and show the error.

      Show
      ASSERT: Have a project (jboss-kitchensink from EAP template) in workspace. EXEC: Create a new application using jboss eap template and kitchensink project (CONTEXT_DIR param is equal to kitchensink) ASSERT: In Import wizard user is asked to provide alternative git repo if it already exists or reuse the existing one. You can choose different git clone location or reuse the one (it does not matter). EXEC: Finish the import wizard. RESULT: Application is trying to import a project to workspace but it fails and show the error.

      Description

      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:

      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.
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jeffmaury Jeff MAURY
                Reporter:
                mlabuda Marián Labuda
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: