Skip to content

Commit

Permalink
#1115 - Switch to UIMA v3
Browse files Browse the repository at this point in the history
- Force all tests run through surefire to use the old UIMAv2 FeatureStructure string serialization
  • Loading branch information
reckart committed Mar 22, 2019
1 parent cce3b44 commit f16fbcf
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,8 @@ protected void starting(Description aDescription)
methodName = aDescription.getMethodName();
System.out.println("\n=== " + methodName + " =====================");

// V2 FS toString needed for CasDumpWriter
// V2 FS toString needed for CasDumpWriter. Also see comment in the root-level pom.xml
// file where this property is globally set for all surefire runs
System.setProperty(FeatureStructureImplC.V2_PRETTY_PRINT, "true");

// Route logging through SLF4J
Expand Down
12 changes: 12 additions & 0 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -626,6 +626,18 @@
<configuration>
<systemPropertyVariables>
<dkpro.core.testCachePath>${dkpro.core.testCachePath}</dkpro.core.testCachePath>
<!--
UIMAv3 changes the default string serialization of feature structures which we rely
on in the CasDumpWriter. To minimize the differences between the DKPro Core UIMAv2
and UIMAv3 branches, we force UIMAv3 to use the old serialization. We also do this
in the DkproTestContext, in particular since your IDE usually won't pick up the
property we set here. But we also set it here because whether or not setting the
value in DkproTestContext has an effect depends on the order in which the tests
are executed. I.e. if a loading the FeatureStructureImplC class is executed while
the property has not been set yet, then it is impossible for a later test to turn
it on.
-->
<uima.v2_pretty_print_format>true</uima.v2_pretty_print_format>
</systemPropertyVariables>
</configuration>
</plugin>
Expand Down

0 comments on commit f16fbcf

Please sign in to comment.