[
https://issues.jboss.org/browse/JBIDE-11454?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11454.
---------------------------------
Resolution: Done
pushed to master / beta2.
This now works perfectly in almost all cases. I will note one case where the results may
be misleading.
If you have a version of your webapp deployed, and it is deployed properly with no errors,
and you publish a new version, AND the new version fails to deploy for some reason, the
view will NOT show the error. Why? Because the application server has
"rolled-back" your change. This means that your previous version is now alive
and responding, and my attempts to query over management whether an app is successfully
started under that name returns 'true'.
So, in this specific case, there's no way for me to propagate the error information.
Make the status of modules be closer to reality
-----------------------------------------------
Key: JBIDE-11454
URL:
https://issues.jboss.org/browse/JBIDE-11454
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Environment: JBoss Developer Studio 5 Beta
JBoss Enterprise Application 6 Beta
Reporter: Mustafa Musaji
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.1.0.Beta2
When deployment of an application fails on JBoss EAP, JBoss Tools doesn't recognize
this as failure and continues to report the status as [Started, Synchronized].
This a request to add the ability for JBDS to report back via the console when a
deployment fails due to application errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira