-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
JBIDE-11509, AS7-783 and TORQUE-576 all talk about the problem of all deployments found at startup is deployed in one operation and if one deployment fails all is rolled back resulting in some rather bad usability issues - especially at development time, but even also at production time for those using file deployments.
Suggestion on irc was that there could be an option on the file scanner (possibly false by default?) to say that failure causes rollback.
Individual deployments could then still fail, but at least not everything would be rolledback and it would still allow proper interdependent deployments to work.
- is related to
-
JBIDE-11509 Starting the AS/EAP when it already has multiple projects deployed
-
- Closed
-
-
AS7-783 Deployment scanner service should use a separate operation for each deployment
-
- Resolved
-
- relates to
-
-
- Resolved
-
