Quarkus maven plugin seems to ignore my mainClass setting

It seems that at some point between versions 0.22.0 and 1.0.0.CR1, Quarkus maven plugin stopped recognizing settings such as:

<configuration>
    <mainClass>biz.karms.quarkus.json.formatter.Main</mainClass>
</configuration>

Platform

• graalvm-ce-19.1.1 Linux x86_64
• Apache Maven 3.6.0
• OpenJDK 11

Steps to reproduce:

• clone https://github.com/Karm/qjf.git
• mvn clean package -Pnative
• get some json file and let it format it:
• curl https://starter.karms.biz/api/supportMatrix | ./target/qjf-runner

It works as long as the version is e.g. 0.22.0 (which is in the aforementioned repo):

karm@local:~/workspaceRH/qjf $ cat ugly.json | ./target/qjf-runner

{
    "configs": {
        "MP30": {
            "supportedServers": [
                "LIBERTY",
<SNIP>

It breaks if you change Quarkus version in the pom.xml to e.g. 1.0.0.CR1:

By “it breaks” I mean that my Main class is ignored and the generated Quarkus one is used.

(base) karm@local:~/workspaceRH/qjf ((v1.0) *%)$ cat ugly.json | ./target/qjf-runner
2019-11-07 15:33:07,322 INFO  [io.quarkus] (main) qjf 1.0.0-SNAPSHOT (running on Quarkus 1.0.0.CR1) started in 0.001s.
2019-11-07 15:33:07,322 INFO  [io.quarkus] (main) Profile prod activated.
2019-11-07 15:33:07,322 INFO  [io.quarkus] (main) Installed features: []

...hangs....

^C

2019-11-07 15:33:09,139 INFO  [io.quarkus] (main) qjf stopped in 0.000s

Is this a configuration thing? Is it a feature or a bug? After some googling around the Quarkus guides I consider this a bug, hence this issue. Thank you for feedback.

[rsvoboda]

It seems that at some point between versions 0.22.0 and 1.0.0.CR1

Last version when qjf worked was 0.25.0

[stuartwdouglas]

This should not be a problem now we have command mode support.