ST6RI-953 Removed logic stand-alone set-up from ParserPostProcessorTest.

- This was adversely interacting with the SysMLInteractiveTest Xtext
setup, so that, in particular, global name resolution sometimes failed.

- This set up is not necessary in the test, because all components
being tested are called directly.

Author: seidewitz

org.omg.sysml.interactive.tests/src/org/omg/sysml/interactive/tests/ParserPostProcessorTest.java

@@ -17,7 +17,6 @@
 import static org.junit.Assert.assertNotSame;
 import static org.junit.Assert.assertTrue;
 
-import org.junit.BeforeClass;
 import org.junit.Test;
 import org.omg.kerml.xtext.postprocessing.ElementParserPostProcessor;
 import org.omg.kerml.xtext.postprocessing.ImportParserPostProcessor;
@@ -40,19 +39,11 @@
 import org.omg.sysml.lang.sysml.PortUsage;
 import org.omg.sysml.lang.sysml.PortionKind;
 import org.omg.sysml.lang.sysml.SysMLFactory;
-import org.omg.sysml.lang.sysml.SysMLPackage;
 import org.omg.sysml.lang.sysml.Usage;
-import org.omg.sysml.logic.SysMLLogicStandaloneSetup;
 import org.omg.sysml.util.TypeUtil;
 
 public class ParserPostProcessorTest extends SysMLInteractiveTest {
 
-	@BeforeClass
-	public static void setUp() {
-		SysMLLogicStandaloneSetup.doSetup();
-		SysMLPackage.eINSTANCE.eClass();
-	}
-
 	@Test
 	public void factorySelectsTheMostSpecificParserPostProcessorWithoutAttachingIt() {
 		PortUsage port = SysMLFactory.eINSTANCE.createPortUsage();