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

Cloning an app with invalid pom results no project imported to your workspace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • 4.2.0.Alpha1
    • 3.3.0.M4
    • openshift
    • None
    • Hide

      1) EXECUTE: create a new jbossas-7.0 (cartridge/type) application on OpenShift
      2) EXECUTE: import the project to the local workspace
      3) EXECUTE: change the pom to get invalid (ex. add a 2nd <profiles> tag)
      4) EXECUTE: commit and push upstream (using EGit or server adapter)
      5) EXECUTE: remove your local git clone and the proj from your workspace
      6) EXECUTE: remove the server adapter for your project
      6) EXECUTE: import your project again using the OpenShift Express wizard

      Result:
      You end up having the git clone, but no project is imported to your workspace (the maven import fails since the pom is invalid)

      Expected:
      You end up having a general project in your workspace. The import informs you that the maven project could not be imported since the pom was invalid. It also tells you that the project is imported as "general project" instead.

      Show
      1) EXECUTE: create a new jbossas-7.0 (cartridge/type) application on OpenShift 2) EXECUTE: import the project to the local workspace 3) EXECUTE: change the pom to get invalid (ex. add a 2nd <profiles> tag) 4) EXECUTE: commit and push upstream (using EGit or server adapter) 5) EXECUTE: remove your local git clone and the proj from your workspace 6) EXECUTE: remove the server adapter for your project 6) EXECUTE: import your project again using the OpenShift Express wizard Result: You end up having the git clone, but no project is imported to your workspace (the maven import fails since the pom is invalid) Expected: You end up having a general project in your workspace. The import informs you that the maven project could not be imported since the pom was invalid. It also tells you that the project is imported as "general project" instead.
    • Hide
      • checkout manually from git repo that was cloned, correct the pom and commit. Then push the local git clone to upstream.
      • you can also import the proj manually from your local git clone as general project, correct pom and enable Maven nature.
      Show
      checkout manually from git repo that was cloned, correct the pom and commit. Then push the local git clone to upstream. you can also import the proj manually from your local git clone as general project, correct pom and enable Maven nature.

          adietish@redhat.com André Dietisheim
          adietish@redhat.com André Dietisheim
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

            Created:
            Updated:
            Resolved: