Issues using the new Maven's quarkus packaging with native console application. what to do ?

[cvgaviao]

Hello.

I changed the packaging type from jar to quarkus on our microservices and everything was ok.

And today I tried to do the same for our native image based console applications. But their Jenkins pipelines started to fail.

The reason is that the new quarkus packaging's lifecycle doesn't contains maven-install-plugin nor maven-deploy-plugins goals associated to it.

So, doing a "mvn deploy" doesn't calls deploy:deploy...

I tried to attach the maven-deploy-plugin in the project's pom, but it fails because this plugin needs to have something which is produced by the maven jar or install plugin and added to the build context, so it didn't work.

I also noted that build-helper-maven-plugin, which is used to attach the generated native image to the project's artifacts, also didn't work.

So, for now I've rollback the changes.

Anyone have experience this kind of issues and fixed ?

[quarkus-bot[bot]]

/cc @quarkusio/devtools (maven)