-
Bug
-
Resolution: Done
-
Major
-
4.1.0.Beta1
-
None
Since the maven import (not git clone) failed due to corrupt pom.xml we could add general hint to check the pom.xml to the error description.
<adietisheim> maxandersen1: the suggestion is to add a text to the details that tells the user to closely inspect the pom in the cloned repo. The maven import failed so it's very like there was something wrong with the pom.
<adietisheim> we know where the stuff was cloned to, we could point the user to that location in the details
<adietisheim> and tell it to inspect the pom there
- is related to
-
JBIDE-14546 Could not import maven project when creating jbossews apps (WATCHER ISSUE)
- Closed
-
JBIDE-13769 Import maven project fails: "Could not import project null"
- Closed