Merge pull request #582 from jam01/mule-4-jdk11

removes mule-4 jdk11 override

Author: Sergei Malafeev

test/mule/mule-4-app/pom.xml

@@ -29,6 +29,33 @@
   <properties>
     <exec.skip>true</exec.skip>
   </properties>
+  <profiles>
+    <profile>
+      <id>jdk11-compat</id>
+      <activation>
+        <jdk>11</jdk>
+      </activation>
+      <!-- This could be a bug with Mule 4 class loading mechanism behaving differently between
+      JDK 1.8 and 11, or an oversight on mule-4-artifact-module instrumentation. To be determined... -->
+      <dependencies>
+        <dependency>
+          <groupId>io.opentracing</groupId>
+          <artifactId>opentracing-api</artifactId>
+          <scope>provided</scope>
+        </dependency>
+        <dependency>
+          <groupId>io.opentracing</groupId>
+          <artifactId>opentracing-noop</artifactId>
+          <scope>provided</scope>
+        </dependency>
+        <dependency>
+          <groupId>io.opentracing</groupId>
+          <artifactId>opentracing-util</artifactId>
+          <scope>provided</scope>
+        </dependency>
+      </dependencies>
+    </profile>
+  </profiles>
   <build>
     <plugins>
       <plugin>

test/mule/mule-4.2.2/src/test/java/io/opentracing/contrib/specialagent/test/Mule4ContainerITest.java

@@ -21,11 +21,6 @@ public class Mule4ContainerITest {
   private static final String MULE_HOME = "/src/test/mule-home";
 
   public static void main(final String[] args) throws Exception {
-    if (!System.getProperty("java.version").startsWith("1.8.")) {
-      System.err.println("This test is not working: https://github.com/opentracing-contrib/java-specialagent/issues/405");
-      return;
-    }
-
     final String homeDir = new File("").getAbsolutePath() + MULE_HOME;
     final Mule4ContainerITest lock = new Mule4ContainerITest();
     System.setProperty(MuleSystemProperties.MULE_SIMPLE_LOG, "true");