[
https://issues.jboss.org/browse/JBAS-8550?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on JBAS-8550:
----------------------------------------
The FS scanner adds "rollback-on-runtime-failure"=>"true" to the
composite operation it generates for each scan. If a .faileddeploy is present, that means
the operation was rolled back. Possibly unsuccessfully, but the normal behavior would not
be to leave services sitting around that can be retried later.
It's certainly true that people should not use the FS scanner marker files as a
substitute for querying the real server model. I'll note that in the README.txt. If I
hear between now and GA that anyone is trying to create automated tooling based on reading
them, I'll remove them.
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