Test build targets for modules

[GoogleCodeExporter]

Build system should include test targets to facilitate Test-Driven Development.

Original issue reported on code.google.com by pympno...@gmail.com on 7 Feb 2012 at 7:00

[GoogleCodeExporter]

Starting point for running tests in modules. See attached diff for 
/wonderland-trunk/modules/build-tools/build-scripts/module-build.xml

Original comment by pympno...@gmail.com on 7 Feb 2012 at 7:02

Attachments:

• module-build.xml.diff

[GoogleCodeExporter]

Added core libraries and module-defined libraries to test compile and run 
classpaths. Please see attached diff.

Original comment by pympno...@gmail.com on 8 Feb 2012 at 4:27

Attachments:

• module-build.xml.diff

[GoogleCodeExporter]

Jon to commit for April 2012 release.

Original comment by jonathan...@gmail.com on 27 Mar 2012 at 5:31

• Added labels: Milestone-0.5-April2012

[GoogleCodeExporter]

Update milestone

Original comment by jonathan...@gmail.com on 24 Apr 2012 at 9:54

• Added labels: Milestone-0.5-May2012
• Removed labels: Milestone-0.5-April2012

[GoogleCodeExporter]

Updated diff
 - include libraries in core
 - proper integration of test classpaths
 - create macro for running tests

Original comment by jonathan...@gmail.com on 27 Apr 2012 at 9:43

Attachments:

• test-build.zip

[GoogleCodeExporter]

This issue was closed by revision r4839.

Original comment by jonathan...@gmail.com on 30 Apr 2012 at 6:01

• Changed state: Fixed