Chaining mvn clean to the quarkus:build goal corrupts the output

[kb1892]

I've spent quite a while trying to debug my Quarkus project to no avail and finally figured out that it was a Maven issue that was corrupting the build. I'm building a lambda using the lambda-http extension, and kept on getting 404 not found for every single path I set up on the resource, whether running in jar mode or native compile. It turns out that the compiled binaries were being corrupted some how by chaining the clean goal to the quarkus:build goal like this: mvn clean quarkus:build -U -Dnative -DskipTests. How I figured out something was happening weird with the build process was because I have compression enabled in my app.properties, but I noticed that UPX was never being invoked. As soon as I ran these three commands separately - mvn clean, mvn package -U, mvn quarkus:build -Dnative -DskipTests, everything compiled, UPX ran, and my lambda paths in proxy mode worked as expected. My question boils down to this am I not supposed to chain these two goals together, or is there something else going on?