[
https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-11509:
-------------------------------------
I have found that simply having previous deployments on the server, stopping it,
restarting the IDE, then using Run As Run on Server on the stopped server (with a
deployments folder full of previously deployed apps) will also demonstrate the problem. I
can see how this would throw off a newbie who thought his previously deployed apps that
were once successful, now fail.
I made a video of the flow that I use - this hits me regularly
http://screencast.com/t/YyQ31jCOnYy
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