- improved and renamed common-os::assert_pre_requisite to
  assert_commands_available.

  The function now takes a list of commands to check for and prints
  errors for each of these before exiting in error -- if any errors
  were encountered.

  Example usage: assert_commands_available mysqldump jar java gzip

- updated all modules that used common-os::assert_pre_requisite to use
  the new common-os::assert_commands_available. This also simplified
  the implementations here and there as they themselves had
  implemented the looping of commands to check for.
- Fixed regression bug: /etc/default/ece is no longer included in the
  escenic-content-engine-scripts package.

  - It is no included in the escenic-content-engine-scripts under
    /usr/share/doc/escenic/escenic-content-engine-scripts/examples/etc/default/ece
    instead.

  - If /etc/default/ece isn't available on the system to be
    installed (such as pure, fresh system) ece-install will test to
    see if the examples file is there and if yes, use it. If the file
    is not there, ece-install will generate a simple one (without
    comments).

- long overdue cleanup: removed the use of get_boolean_conf_value in
  favour of doing a regular BASH evaluation with fall back values
  directly in the statement. This reduces code size and maintenance
  time of own utility methods. Yah!
- re-implemented the way rollback handles the publication resources
- hardening
- log needs to be set since system-info modules might use the run (and
  other) common-bashing wrappers which requires this variable to be
  set.
- copying of conf files must be -rf to that it'll overwrite read only
  files, if present.
- common-io::download_uri_target_to_dir no longer returns the
  downloaded artifact as a return value from the function. This is
  because it uses the run wrapper inside, which in turn will report
  any problems when e.g. downloading the requested resource.

  The downside of this, is that the calling functions must take care
  of constructing the location of the downloaded artifact themselves,
  it'll always be $dir/$uri, as in:

     download_uri_target_to_dir $uri $dir

  so it shouldn't be too hard :-)

- changed ece-import::http-and-ftp, ece-install::app-server,
  ece-install::content-engine, ece-install::create-publication,
  ece-install::search-server and ece::deploy to use the new
  common-io:: download_uri_target_to_dir without this return
  value.

  This gain of this, is that any problems with the download will be
  reflected in the calling script and not being swallowed in the
  subshell that the calling functions would spawn when calling
  common-io::download_uri_target_to_dir
- changed the default ECE instance name from web1 to engine1 as this
  is what we're using for our SaaS

- updated all examples and documentation to refer to the new name
- common-io::download_uri_target_to_dir now includes the HTTP response
  headers. This is very useful, for instance when the download fails
  because of authorisation. This information will be present in the
  logs.
- ece-deploy was wiping away any http_proxy environment variable that
  was set in the SHELL :-(
editing, plus added new stuff on jira and subversion
Merge branch 'master' of github.com:skybert/ece-scripts