[
https://issues.jboss.org/browse/JBAS-8550?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-8550:
-----------------------------------
I disagree with this issue. A deployment failure is always a potentially transient
condition - the service which failed can always be retried etc. Deployments are either in
or out. That's all.
To look at it from another angle - a deployment which *isn't* failed can become failed
by removing a deployment it depends on. This need not and should not be reflected in the
filesystem, whose only role is ultimately to provide content for a deployment, not to
necessarily represent the deployment itself or to reflect the status of a deployment in
the server model.
Filesystem deployment service should use a different marker file for
failed deployments
---------------------------------------------------------------------------------------
Key: JBAS-8550
URL:
https://issues.jboss.org/browse/JBAS-8550
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
From Jesper Pedersen:
Shouldn't a deployment which fails be called .failed instead of .deployed ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira