[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-9101) AS7: Deployments should not be restarted for incremental deployments
Andre Dietisheim (JIRA)
jira-events at lists.jboss.org
Fri Jun 10 06:29:59 EDT 2011
[ https://issues.jboss.org/browse/JBIDE-9101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607459#comment-12607459 ]
Andre Dietisheim edited comment on JBIDE-9101 at 6/10/11 6:28 AM:
------------------------------------------------------------------
weird enough I cannot replicate the behavior from the prior comment with manual steps, but I experience other strange things:
# make sure you have a exploded war deployed to as7 beta3
# change it's web.xml to something invalid
# watch the server log to see if there's any change in the deployment state (according to the above comment as7 should pick the change and undeploy the artifact)
Result:
AS7 does not change the state of the deployment, it does not pick the change.
# now change a resource in your deployment (ex. index.html)
Result:
AS7 now delivers the changed resource.
# now clean
Result:
The app is not available any more, you get a 404. The deployment folder has a .deployed marker though.
# now change the web.xml to something valid again and clean.
Result:
The app is accessible but the deployment folder has a .failed now.
was (Author: adietish):
weird enough I cannot replicate the behavior from the prior comment with manual steps:
# make sure you have a exploded war deployed to as7 beta3
# change it's web.xml to something invalid
# watch the server log to see if there's any change in the deployment state (according to the above comment as7 should pick the change and undeploy the artifact)
Result:
AS7 does not change the state of the deployment, it does not pick the change.
# now change a resource in your deployment (ex. index.html)
Result:
AS7 now delivers the changed resource.
# now clean
Result:
The app is not available any more, you get a 404. The deployment folder has a .deployed marker though.
# now change the web.xml to something valid again and clean.
Result:
The app is accessible but the deployment folder has a .failed now.
> 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: Rob Stryker
> 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
More information about the jbosstools-issues
mailing list