[
https://issues.jboss.org/browse/JBIDE-9101?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-9101:
------------------------------------
Steps to Reproduce:
# make sure you have a project that is deployed to an as7 that you run (ex. create a
Dynamic Web Project from scratch, add a index.html file to the WebContent folder)
# change a single file in your project (ex. index.html)
Result:
You see in the server log that the deployment is being restarted
(ex. my project is called bogus and I catch the following in the server log when changing
index.html:
{code}
23:02:25,075 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting
deployment of "bogus.war"
23:02:25,298 INFO [org.jboss.web] (MSC service thread 1-7) registering web context:
/bogus
{code}
Expected:
The deployment should not get restarted. The file should get replaced by the new one and
picked by AS7 instantly (without a restart of the deployment).
was:
# make sure you have a project that is deployed to an as7 that you run (ex. create a
Dynamic Web Project from scratch, add a index.html file to the WebContent folder)
# change a single file in your project (ex. index.html)
Result:
You see in the server log that the deployment is being restarted
(ex. my project is called bogus and I catch the following in the server log when changing
index.html:
{code}
23:02:25,075 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting
deployment of "bogus.war"
23:02:25,298 INFO [org.jboss.web] (MSC service thread 1-7) registering web context:
/bogus
{code}
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