Split up the tests project into sub-projects

[GoogleCodeExporter]

What new or enhanced feature are you proposing?
Split up the large .tests project into smaller projects:

.tests.release
.tests.inference
.tests.codegen

The .tests project can then combine all of these tests together.

What goal would this enhancement help you achieve?
By using the Eclipse framework more effectively, tests should be faster to
run (i.e. we shouldn't need to load Drools in order to run the release
tests, or OAW to run the inference tests).

Original issue reported on code.google.com by soundasleep on 10 Feb 2010 at 1:35

• Blocking: #146, #106, #71

[GoogleCodeExporter]

moving all unresolved 0.5 issues to 0.6

Original comment by soundasleep on 17 Apr 2010 at 6:58

• Added labels: Milestone-Release0.6

[GoogleCodeExporter]

mass tagging old issues to future work

Original comment by soundasleep on 26 Sep 2011 at 9:54

• Added labels: Milestone-Release0.7