chore: Migrate to Java 11

[jdneo]

Now that the Java Language Support Extension has embedded JRE 17 to run all Java extensions, it's time to migrate to Java 11.

Signed-off-by: Sheng Chen [email protected]

[testforstephen]

The compiler version in some pom.xml is still 1.8.

vscode-java-test/java-extension/com.microsoft.java.test.runner/pom.xml

Lines 30 to 35 in 78717ac

	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-compiler-plugin</artifactId>
	<version>3.1</version>
	<configuration>
	<source>1.8</source>
	<target>1.8</target>

[jdneo]

The compiler version in some pom.xml is still 1.8.

That's the test runner for TestNG, which is just a common Java Application, not a OSGi bundle. So I think it's fine to keep it as 1.8

[testforstephen]

I don't see you specify compiler version explicitly in your plugin pom.xml, I'm curious what's the target Java version when you're compile artifacts from cmd.

If there are 1.8 and 11 mixed in the final build artifacts, I'd rather not update to 11.

[karlvr]

@jdneo This line in JUnitLaunchConfigurationDelegate.java uses Set.of which is not available in Java 1.8, but the maven compiler plugin is set to use Java 1.8:

private static final Set<String> testNameArgs = Set.of("-test", "-classNames", "-packageNameFile", "-testNameFile");

So I think the Java version in the pom.xml referenced above might need to be updated to 11?