[
https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11509:
---------------------------------------------
Snjezana - great if you got a fix; we should make sure that get into AS.
But that issue is *not* the problem this issue is about - this issue is simply about how
users can recover from 1 out of many apps have failed deployment.
Rob - that is easy to reproduce by simply introducing an error in one of your war's
(i.e. refer to a datasource that does not exist) and all the modules in deployment will be
rolled back. we need users to be able to see deployment fails for modules (JBIDE-11454)
and then be able to actually fix it - i.e. be able to deploy modules individually
...actually if we fix JBIDE-11454 we actually got a good way for users to recover from
startup failures.
Starting the AS/EAP when it already has multiple projects deployed
------------------------------------------------------------------
Key: JBIDE-11509
URL:
https://issues.jboss.org/browse/JBIDE-11509
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Burr Sutter
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
Attachments: jbide-11509.patch, poh5.war.failed, startup_log.txt,
weld-core-1.1.5.AS71.Final.jar
When the server is started via "Run As on Server", and there were previous
projects deployed (both inside/outside of the IDE), they tend to all fail to start.
--
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