[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9101) AS7: Deployments should not be restarted for incremental deployments
[
https://issues.jboss.org/browse/JBIDE-9101?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-9101:
-----------------------------------------
I noticed a strange behavior in as7:
If I cripple the web.xml (ex. remove a closing xml so that it gets invalid), and do not
create a new .dodeploy marker, the server stops the deployment and creates a .undeployed.
Our prior implementation, which created a .dodeploy even for incremental changes, had as7
creating a .failed marker instead.
AS7: Deployments should not be restarted for incremental deployments
--------------------------------------------------------------------
Key: JBIDE-9101
URL: https://issues.jboss.org/browse/JBIDE-9101
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.M2
Currently, if you have a project deployed to AS7 and change a single file, the deployment
gets restarted (a new .dodeploy marker is created). This should not happen. Deployments
should only be (re-)started (a .dodeploy marker created) in the following cases:
# new deployment
# cleaning
# full publish
# restarting
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira