Description of properties isn't good enough - not clear enough. This has to be changed later
Added a custom Output task, that can write to the console, without using Phing's logging
Added a end of line output test
Changed PHPDoc
Added a outputTask-help target, so that developers can get some help directly in the console
Importing the output recipe - However, there is another path bug. It attempts to load the properties file again.
Rearranged the file structure - more fitting to keep every task def together with their help/test/debug targets
Fixed #46: Attempt to load already loaded properties file, in output.xml
Fixed #49: Indentation is too much
Changed property name
New Task for getting a complet list of available targets, including information about the target's origin (Not yet finished)
Added the availableTargetList-test, for manually testing the new task
Made some progress - however, it doesn't seem that the projects are correctly loaded...!?
A wrong path prohibited project configuration. However, now the projects seem to be executing something, which isn't what was needed!
Managed to actually get hold of the targets, based upon the import stack - which is exactly what is needed. Now, the task needs to be split into more manageable methods
Removed the includes - they are already available through the Phing class
Created a new data structure that contains the desired information about the projects/build-files, and what targets are available
Implemented #50: Var dump print
Added a isLoaded property for the build script - can be used to check if this build script is already loaded inside another
Task is now able to store the available targets list to a user-provided property