fix: for #1611

Only execute concurrent tests with VMLens:
VMLens test run now takes 2s and there is no risk of hanging tests.
The hanging tests was during executing ArchUnitTests with VMLens.

Renamed  VmLensTest to VmLensCT and added a filter in the VMlens plugin.

Signed-off-by: Thomas Krieger [email protected]

Author: ThomasKrieger

pom.xml

@@ -348,7 +348,7 @@
             </activation>
             <build>
                 <plugins>
-                    <!--<plugin>
+                    <plugin>
                         <groupId>com.vmlens</groupId>
                         <artifactId>vmlens-maven-plugin</artifactId>
                         <version>1.2.14</version>
@@ -359,11 +359,14 @@
                                     <goal>test</goal>
                                 </goals>
                                 <configuration>
+                                	<includes>
+						                <include>**/*CT.java</include>
+					                </includes>
                                     <failIfNoTests>true</failIfNoTests>
                                 </configuration>
                             </execution>
                         </executions>
-                    </plugin>-->
+                    </plugin>
                     <plugin>
                         <artifactId>maven-dependency-plugin</artifactId>
                         <version>3.8.1</version>

src/test/java/dev/openfeature/sdk/vmlens/VmLensTest.java renamed to src/test/java/dev/openfeature/sdk/vmlens/VmLensCT.java

@@ -18,7 +18,7 @@
 import org.junit.jupiter.api.BeforeEach;
 import org.junit.jupiter.api.Test;
 
-class VmLensTest {
+class VmLensCT {
     final OpenFeatureAPI api = OpenFeatureAPITestUtil.createAPI();
 
     @BeforeEach