unknown author

[Jorge]

I recently setup a new computer and forgot to configure my username in
git, so my last post on GitHub shows "unknown" as the author of the
post for today :)

The following are my commit notes, the biggest changes are in regards
to nested builds and the "use_exit_on_error" variable:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
* Added new $psake variable called "build_script_dir" that can be used
to quickly get the directory that the build script is executing from

* Fixed issue where a nested build that fails did not re-throw the
exception to the parent build

* Updated psake.ps1 so that the try/finally is removed and the call to
"remove-module" is the first thing that is done

* Removed $psake variable "use_exit_on_error" - The code now detects
if it was launched via a windows service and assumes that the exit()
function should be used. Most of the popular continuous build engines
(Hudson, TeamCity, Cruise Control.net etc..) that are in use are
hosted by a windows service of some kind (IIS, Apache, etc....). When
psake encounters an exception in the build script it checks using a
new
private module function called "IsChildOfService()" to determine if
it's ancestor's process was a windows service, if it was then it calls
the exit() function with a value of "1".

* Removed the "use_exit_on_error" $psake variable since it is no
longer needed

* Updated "specs\writing_psake_variables_should_pass.ps1" to include
new "build_script_dir" and removed reference to the
"use_exit_on_error" variable

* Changed the $psake variable "suppress_error_messages" to
"run_by_psake_build_tester" - this is a control variable used by the
psake-BuildTester.ps1 script
------------------------------------------------------------------------------------------------------------------------------------------------------------

The next thing I'm looking at is adding a psake.config file that can
be used to control the following:

1) What directory or directories to look for modules to load
2) A setting to change what exit code to use when a build fails
(default = 1)
3) What the default build script name should be
4) Default format for the task name

I'm not sure if the psake.config will be in xml format or not -
although I'm leaning towards that direction.

Feel free to reply with ideas or comments!