[jbosstools-commits] JBoss Tools SVN: r31123 - trunk/tests/plugins/org.jboss.tools.tests/src/org/jboss/tools/test/util.

[jbosstools-commits at lists.jboss.org]

Author: vrubezhny
Date: 2011-05-06 08:01:18 -0400 (Fri, 06 May 2011)
New Revision: 31123

Modified:
   trunk/tests/plugins/org.jboss.tools.tests/src/org/jboss/tools/test/util/ResourcesUtils.java
Log:
JBIDE-8869
5 tests in JSF component failed with the same error in tearDown() method

fix is committed

Modified: trunk/tests/plugins/org.jboss.tools.tests/src/org/jboss/tools/test/util/ResourcesUtils.java
===================================================================
--- trunk/tests/plugins/org.jboss.tools.tests/src/org/jboss/tools/test/util/ResourcesUtils.java	2011-05-06 07:04:07 UTC (rev 31122)
+++ trunk/tests/plugins/org.jboss.tools.tests/src/org/jboss/tools/test/util/ResourcesUtils.java	2011-05-06 12:01:18 UTC (rev 31123)
@@ -203,7 +203,14 @@
 	public static void deleteProject(String projectName) throws CoreException {
 		IResource member = ResourcesPlugin.getWorkspace().getRoot().findMember(projectName);
 		if (member != null) {
-			member.getProject().delete(true, true, null);
+			try { 
+				member.getProject().delete(true, true, null); 
+			} catch (Exception e) {
+				// Ignore any exceptions here (mostly because ResourceException rising is possible here)
+				// But we cannot break tearDown() procedures in test cases which widely use this method
+				// So, just print an exception stacktrace to see it in console log
+				e.printStackTrace();
+			}
 		}
 	}