[
https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11509:
---------------------------------------------
Burr, we should *never* undeploy all previously deployed apps automatically. Users point
these on production or test servers and boom you just removed their deployments - or even
if dev, might remove deployments tools have not had any interaction with. So that is a no
go - we need to find a better way to handle this. i.e. make it possible to see what
deployments are failed easily or have a "clean deployements" directory option.
And I've only seen this fail when I actually had a war being failing to deploy before
restarting.
If you have example of otherwise then I'll for sure would like to know.
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
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