</properties>
          <promoteUserPropertiesToSystemProperties>false</promoteUserPropertiesToSystemProperties>
          <systemPropertyVariables>
            <maven.home>${basedir}/src/test/resources/mavenHome</maven.home>
            <userHome>${basedir}/src/test/resources/userHome</userHome>
            <userDir>${basedir}/src/test/resources/userDir</userDir>
          </systemPropertyVariables>

                if (mavenArtifactJar.matcher(filename).matches()) {
                    Process p = Runtime.getRuntime().exec(new String[] {
                        Paths.get(System.getProperty("java.home"), "bin/java").toString(),
                        "-jar",
                        file.toAbsolutePath().toString(),
                        "5.32",
                        "5.27"
                    });

 * This is not correct as it should do this with the built distribution instead.
 *
 * Doing it correctly would require running a Gradle build with the full
 * distribution and extracting the generated api jar from its Gradle user home,
 * slowing down building documentation.
 *
 * All this would be so much simpler if the Kotlin extensions to the Gradle API
 * were generated at build time instead.
 *

        return sessionBuilder;
    }

    private Path resolve(String string) {
        if (string.startsWith("~/") || string.startsWith("~\\")) {
            // resolve based on $HOME
            return Paths.get(System.getProperty("user.home"))
                    .resolve(string.substring(2))
                    .normalize()
                    .toAbsolutePath();
        } else {
            // resolve based on $CWD

             Searching for package file structure from directories
             with <font color="#3465A4">__init__.py</font> files
             Importing from <font color="#75507B">/home/user/code/</font><font color="#AD7FA8">awesomeapp</font>

   <span style="background-color:#007166"><font color="#D3D7CF"> module </font></span>  🐍 main.py

        if (Files.exists(normal)) {
            jtc.setJavaHome(Paths.get(javahome.getValue()).normalize().toString());
        } else {
            throw new MisconfiguredToolchainException(
                    "Non-existing JDK home configuration at " + normal.toAbsolutePath());
        }

        return jtc;
    }

    @Override
    public ToolchainPrivate createDefaultToolchain() {

 Maven installation configuration with per-user configuration for example:
 <<<$\{maven.conf}/logging>>> directory was added to core's classpath (see <<<$\{maven.home}/bin/m2.conf>>>). See your implementation
 documentation for details on file names, formats, and so on.

  echo [DEBUG]   "%JAVACMD%" %INTERNAL_MAVEN_OPTS% %MAVEN_OPTS% %JVM_CONFIG_MAVEN_OPTS% %MAVEN_DEBUG_OPTS% --enable-native-access=ALL-UNNAMED -classpath %LAUNCHER_JAR% "-Dclassworlds.conf=%CLASSWORLDS_CONF%" "-Dmaven.home=%MAVEN_HOME%" "-Dmaven.mainClass=%MAVEN_MAIN_CLASS%" "-Dlibrary.jline.path=%MAVEN_HOME%\lib\jline-native" "-Dmaven.multiModuleProjectDirectory=%MAVEN_PROJECTBASEDIR%" %LAUNCHER_CLASS% %MAVEN_ARGS% %*
)

"%JAVACMD%" ^

    <profile>
      <id>print-java-11-home</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.mvnsearch</groupId>
            <artifactId>toolchains-maven-plugin</artifactId>

    <profile>
      <id>print-java-11-home</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.mvnsearch</groupId>
            <artifactId>toolchains-maven-plugin</artifactId>