`//RUNTIME_OPTIONS` not honoured to try and set legacy resolver in Quarkus

[holly-cummins]

I'm not entirely sure if this is a Quarkus issue or a JBang issue, so raising it here to start.

I'm finding that I can't use //RUNTIME_OPTIONS -Dquarkus.bootstrap.legacy-model-resolver=true to set the legacy runtime resolver in Quarkus. I don't know if other runtime options are also affected, or if it's something specific to when this is read and bootstrapped (the latter, I suspect).

To reproduce:

///usr/bin/env jbang "$0" "$@" ; exit $?
//JAVA 17+
// Update the Quarkus version to what you want here or run jbang with
// `-Dquarkus.version=<version>` to override it.
//DEPS io.quarkus:quarkus-bom:${quarkus.version:999-SNAPSHOT}@pom
//DEPS io.quarkus:quarkus-rest:${quarkus.version:999-SNAPSHOT}

// This should work
//RUNTIME_OPTIONS -Dquarkus.bootstrap.legacy-model-resolver=true                                     
// This shouldn't work, I don't think, but I put it in to be sure
//Q:CONFIG quarkus.bootstrap.legacy-model-resolver=true

import jakarta.enterprise.context.Dependent;
import jakarta.inject.Inject;
import io.quarkus.runtime.annotations.QuarkusMain;
import io.quarkus.runtime.QuarkusApplication;

import java.util.List;
import java.util.Map;

import io.quarkus.runtime.Quarkus;

@QuarkusMain
public class repro implements QuarkusApplication {

    @Override
    public int run(String... args) throws Exception {
        System.out.println("Hello world.");

        return 0;
    }
}

This prints a java 25 warning, but you can see the problem before it gets to that point. You can see it's running with the new resolver because a log statement is printed when using the old resolver, or, to be absolutely sure, you can instrument ApplicationDependencyTreeResolver (old) and ApplicationDependencyResolver (new) with some printlns to show what's being run.

jbang -Dquarkus.bootstrap.legacy-model-resolver=true repro.java also runs with the new resolver, but I'd sort of expect that since that's why the //RUNTIME_OPTIONS option exists.

[wfouche]

This test program shows that //RUNTIME_OPTIONS -Dquarkus.bootstrap.legacy-model-resolver=true when set in a JBang Java program, is detected by the Java VM.

c:\> jbang version
0.137.0

c:\> jbang run -R=-Xmx512m PrintRuntimeOptions.java
[jbang] Building jar for PrintRuntimeOptions.java...

Active JVM Input Arguments:
-Dquarkus.bootstrap.legacy-model-resolver=true
-Xmx512m

Active System Properties (set via -D):
-Djava.specification.version=21
-Dsun.cpu.isalist=amd64
-Dsun.jnu.encoding=Cp1252
-Djava.class.path=C:\Users\werne\.jbang\cache\jars\PrintRuntimeOptions.java.27dd7207344d42f4c164fbbee8b6c2b12cdbe36713fcac1339b5da9bba96535a\PrintRuntimeOptions.jar
-Dquarkus.bootstrap.legacy-model-resolver=true
 ....

Quarkus Property:
quarkus.bootstrap.legacy-model-resolver = true

PrintRuntimeOptions.java

import java.lang.management.ManagementFactory;
import java.lang.management.RuntimeMXBean;
import java.util.List;

//RUNTIME_OPTIONS -Dquarkus.bootstrap.legacy-model-resolver=true

public class PrintRuntimeOptions {
    public static void main(String[] args) {
        RuntimeMXBean runtimeMxBean = ManagementFactory.getRuntimeMXBean();
        List<String> arguments = runtimeMxBean.getInputArguments();

        System.out.println("\nActive JVM Input Arguments:");
        for (String arg : arguments) {
            System.out.println(arg);
        }

        // You can also get system properties, many of which are set via -D options
        System.out.println("\nActive System Properties (set via -D):");
        for (String propertyName : System.getProperties().stringPropertyNames()) {
            // Check if the property was likely set as a command-line -D option
            // (Note: some properties are set internally by the JVM)
            System.out.println("-D" + propertyName + "=" + System.getProperty(propertyName));
        }

        // Display value of property quarkus.bootstrap.legacy-model-resolver
        System.out.println("\nQuarkus Property:");
        System.out.println("quarkus.bootstrap.legacy-model-resolver = " + System.getProperty("quarkus.bootstrap.legacy-model-resolver"));
    }
}

Maybe this is not a JBang related issue?

[holly-cummins]

I'm pretty sure it's specific to the support of this particular property, and it's somewhere in the integration between JBang and Quarkus. But I'm not sure in which codebase. :)

[maxandersen]

The runtime options is set for when the built jar is run.

Sounds like you want the -D set during the build phase ?

Then it's //COMPILE_OPTIONS.

Might still not actually set during the quarkus integration ?