From 30ef77eb28f11cf852cafef45d0121623603c58b Mon Sep 17 00:00:00 2001 From: Kris De Volder Date: Wed, 19 Apr 2017 16:14:09 -0700 Subject: [PATCH] Re-enable tests (still failing or not?) --- .../ide/vscode/commons/maven/SourceJavadocTest.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/headless-services/commons/commons-maven/src/test/java/org/springframework/ide/vscode/commons/maven/SourceJavadocTest.java b/headless-services/commons/commons-maven/src/test/java/org/springframework/ide/vscode/commons/maven/SourceJavadocTest.java index 1b8504975..337f705d8 100644 --- a/headless-services/commons/commons-maven/src/test/java/org/springframework/ide/vscode/commons/maven/SourceJavadocTest.java +++ b/headless-services/commons/commons-maven/src/test/java/org/springframework/ide/vscode/commons/maven/SourceJavadocTest.java @@ -65,7 +65,7 @@ public class SourceJavadocTest { assertEquals(expected, type.getJavaDoc().raw().trim()); } - @Test @Ignore //TODO: why is this sometimes failing in CI build? + @Test //TODO: why is this sometimes failing in CI build? public void parser_testClassJavadocForOutputFolder() throws Exception { MavenJavaProject project = projectSupplier.get(); IType type = project.getClasspath().findType("hello.Greeting"); @@ -122,7 +122,7 @@ public class SourceJavadocTest { assertEquals(expected, method.getJavaDoc().raw().trim().substring(0, expected.length())); } - @Test @Ignore //TODO: why is this sometimes failing in CI build? + @Test //TODO: why is this sometimes failing in CI build? public void parser_testInnerClassJavadocForOutputFolder() throws Exception { MavenJavaProject project = projectSupplier.get(); IType type = project.getClasspath().findType("hello.Greeting$TestInnerClass");