Native image gets generated even when all classes are unchanged / up to date

[rsvoboda]

Native image gets generated even when all classes unchanged / are up to date
maven-compiler-plugin detects that case, quarkus-maven-plugin always runs the build

Discussed in https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/skip.20native.20%28re%29build.2C.20run.20just.20test/near/181113795

mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:create \
    -DprojectGroupId=org.acme \
    -DprojectArtifactId=getting-started \
    -DclassName="org.acme.quickstart.GreetingResource" \
    -Dpath="/hello"

mvn verify -Dnative  # runs the native compilation
mvn verify -Dnative  # second run should not run the native compilation but it runs it

[mkouba]

For the record - the fact that no class has changed does not imply that the native image generation should be skipped - for example you can add extesions, change the configuration, resource files, etc.

It's possible to skip the native image manually. Which is not very practical but sometimes it could be useful ;-)

• configure the maven-failsafe-plugin outside the "native" profile and skip the "native" profile activation for the second run:

  mvn verify -Dnative
  # This one will reuse the existing native image
  mvn verify
  

• configure the maven-failsafe-plugin and do not use the "native" profile at all:

  mvn verify -Dquarkus.package.type=native
  mvn verify
  

[rsvoboda]

you can add extesions, change the configuration, resource files

dev mode can detect these things, standard quarkus build could leverage these capabilities too

workaround with failsafe

I'd rather have mvn verify -Dquarkus.native.skip-build=true for better out-of-the-box experience

[gsmet]

I don’t see how that could become a priority anytime soon.

…

Le 19 nov. 2019 à 17:00, Rostislav Svoboda ***@***.***> a écrit : you can add extesions, change the configuration, resource files dev mode can detect these things, standard quarkus build could leverage these capabilities too workaround with failsafe I'd rather have mvn verify -Dquarkus.native.skip-build=true for better out-of-the-box experience — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[rsvoboda]

I think #5609 addresses this quite well

Native image gets built only once when following commands are used

mvn verify -Dnative
mvn failsafe:integration-test

[rsvoboda]

@mkouba / @gsmet I think this can be closed, 5609 is good enough for me.