-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
The scanner is creating a single composite op for all deployments encountered in a scan, rather than individual ops. The effect is failures in on deployment results in rolling back the others.
This makes some sense when users change things after startup, since multiple changes within one scan are probably related to each other. But it's not the correct behavior at startup, since multiple apps may not be interrelated.
- relates to
-
WFLY-364 a "failure-causes-rollback="false"" attribute for the filesystem scanner
- Closed
-
JBIDE-11509 Starting the AS/EAP when it already has multiple projects deployed
- Closed