[
https://issues.jboss.org/browse/JBIDE-8911?page=com.atlassian.jira.plugin...
]
Koen Aers updated JBIDE-8911:
-----------------------------
Fix Version/s: 3.3.0.Beta1
(was: 3.3.0.M4)
Moving to beta1 because not completely under control yet. The core of the issue is due to
the Forge runtime creating a project for which the name already exists in the parent
folder instead of in some sibling folder.
Forge should not swallow errors
-------------------------------
Key: JBIDE-8911
URL:
https://issues.jboss.org/browse/JBIDE-8911
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Reporter: Max Rydahl Andersen
Assignee: Koen Aers
Priority: Critical
Fix For: 3.3.0.Beta1
When the import of Maven goes wrong (i.e. class incompatible error) Forge doesn't
show anything.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira