[jboss-jira] [JBoss JIRA] (WFLY-1305) A failed deployment that is retried on boot will always succeed

[Toby Crawley (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771662#comment-12771662 ] 

Toby Crawley commented on WFLY-1305:
------------------------------------

To confirm this is still an issue and is unrelated to the Immutant changes, I tried this with a build of wildfly (build from https://github.com/wildfly/wildfly/commit/d72bc66db32b299c1f898005467cefe37742308f) and a broken war file. In doing so, I discovered that any file-scanner-based deployment that fails at startup will succeed, not just prior failed deployments that are retried (I'll update the ticket title to reflect this). I gisted the output and steps I used to recreate at: https://gist.github.com/tobias/8566f990c252cd6cc947

Let me know if I can do anything else to help.
                
> A failed deployment that is retried on boot will always succeed
> ---------------------------------------------------------------
>
>                 Key: WFLY-1305
>                 URL: https://issues.jboss.org/browse/WFLY-1305
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Toby Crawley
>
> When an app is deployed via the deployments/ dir, but fails for some reason, it is marked as failed with a .failed marker and undeployed. When the AS is rebooted, it tries to redeploy the failure. If this deploy also fails, this new deployment *isn't* undeployed, and a .deployed marker is written to deployments.
> This is with the 7.2.0.Final used in Immutant, I've yet to try to build Immutant on top of 8.x.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira