> For the general case Scott suggested us is that we support
executing
> a list of .cli operations during deploy - but that would then be very
> specific for JBoss tools which is why I was having high hopes for the
> support for .cli archives that I believe Jesper was working on since
> that would handle the deploy/undeploy cases in a way that is sharable
> between the various tools - but not sure where that went.
Their are major problems with a CLI deployment:
1. Guaranteeing undeploy actually undoes what it did, which may or may not be possible
2. VM crash forcing a relaunch, forcing re-running non-idempotent operations
3. Lack of visibility into what global state each CLI deployment touches
yeah I understand that. It's the exact same problems users and devs of the various
tools that need to setup and run an app on the server today
- maybe large pieces of this just isn't meant to be automated.
/max
http://about.me/maxandersen