avoid nesting managed suites

Nesting ManagedTestSuite causes duplication in the test output and can
cause side effects with the test timeout watcher.

Change-Id: I861dd587057d8a89a224a31401808ffa5035712e

1 files changed, 12 insertions, 1 deletions

diff --git a/org.eclipse.mylyn.tasks.tests/src/org/eclipse/mylyn/tasks/tests/AllTasksTests.java b/org.eclipse.mylyn.tasks.tests/src/org/eclipse/mylyn/tasks/tests/AllTasksTests.java
index d490fa4dc..1c4070d98 100644
--- a/org.eclipse.mylyn.tasks.tests/src/org/eclipse/mylyn/tasks/tests/AllTasksTests.java
+++ b/org.eclipse.mylyn.tasks.tests/src/org/eclipse/mylyn/tasks/tests/AllTasksTests.java
@@ -15,6 +15,7 @@ import junit.framework.Test;
 import junit.framework.TestSuite;
 
 import org.eclipse.mylyn.commons.sdk.util.ManagedTestSuite;
+import org.eclipse.mylyn.commons.sdk.util.TestConfiguration;
 import org.eclipse.mylyn.tasks.tests.bugs.SupportHandlerManagerTest;
 import org.eclipse.mylyn.tasks.tests.core.FileTaskAttachmentSourceTest;
 import org.eclipse.mylyn.tasks.tests.core.ITasksCoreConstantsTest;
@@ -59,6 +60,17 @@ public class AllTasksTests {
 
 	public static Test suite() {
 		TestSuite suite = new ManagedTestSuite(AllTasksTests.class.getName());
+		addTests(suite);
+		return suite;
+	}
+
+	public static TestSuite suite(TestConfiguration configuration) {
+		TestSuite suite = new TestSuite(AllTasksTests.class.getName());
+		addTests(suite);
+		return suite;
+	}
+
+	public static void addTests(TestSuite suite) {
 		suite.addTestSuite(TasksUiUtilTest.class);
 		suite.addTestSuite(TaskListUiTest.class);
 		suite.addTestSuite(TaskRepositoryCredentialsTest.class);
@@ -146,7 +158,6 @@ public class AllTasksTests {
 		suite.addTestSuite(RepositoryConnectorContributorTest.class);
 		suite.addTestSuite(TaskInitializationDataTest.class);
 		suite.addTestSuite(TaskDataDiffTest.class);
-		return suite;
 	}
 
 }