How to remove or selectively include dependent libraries in Quarkus build for production

Posted on

Liquibase libraries included in Quarkus has vulnerabilities and we need to remove liquibase libraries in my application production image.

We create docker image of my application. We need liquibase for schema migration for unit-testing and "dev" mode only and not for production.
1) mvn quarkus:verify
2) mvn quarkus:dev

How to remove or not include liquibase for "prod" image ?

for unit-testing i could use mvn scope but how to handle for mvn quarkus:dev ??

VM

Responses