Closed aduursma closed 1 year ago
/cc @ebullient (cli), @maxandersen (cli)
Hi Guys,
I understand it is summer holiday season.
Just wondering about any update on the issue...
Tried with 3.2.4, but the issue is still there.
Tried with 3.3.0, but the issue is still there.
@geoand
Any updates on this issue?
Not that I know of
Do you have any special characters in your username or password that could trigger that?
Because I don't see any quotes in:
-Dmaven.repo.local=/agent/_work/2/.m2/repository -f /agent/_work/2/s/pom.xml -B -U -X -s /agent/_work/_temp/interventions-maven-settings.xml -Drevision=SNAPSHOT -DskipTests -Ddocker.skip.run=true -Dquarkus.container-image.push=true -Dquarkus.container-image.username= -Dquarkus.container-image.password= -Pnative install
Not saying it shouldn't be fixed in Quarkus by escaping things more properly but that would help us to understand the issue.
I'm pretty sure that's the issue.
There are one or more special characters in either the username or password.
Unfortunately, the credentials are injected into our pipeline, so I can't view the contents myself.
I tried adding quotes like so:
"-Dquarkus.container-image.username=***" "-Dquarkus.container-image.password=***"
-D"quarkus.container-image.username=***" -D"quarkus.container-image.password=***"
-Dquarkus.container-image.username="***" -Dquarkus.container-image.password="***"
It didn't work.
Tried with 3.4.0, but the issue is still there.
Tried with 3.4.1, but the issue is still there.
Thanks for the update
After 3 months of being unable to upgrade, and getting no feedback whatsoever, I finally took a step back and lowered our security constraints by using a password without any "special" characters in it, so the Quarkus Maven plugin can handle it.
By lowering security I was able to upgrade to Quarkus 3.4.1.
Describe the bug
I have a build step in my CI/CD pipeline for creating and pushing a native image containing my application.
This step works fine with all 3.1.x Quarkus versions.
It stopped working when I upgraded to Quarkus 3.2.0 a while ago.
It doesn't work with Quarkus 3.2.1 and Quarkus 3.2.2 either.
When i revert back to Quarkus 3.1.3 the build step works just fine and creates and pushes the image as usual.
By looking at the logs the issue seems Maven related, not Quarkus, but that doesn't explain why things stop working when all I do is upgrade to the latest Quarkus version.
Hope you guys have any ideas...
Expected behavior
The native image is build and pushed succesfully with Quarkus 3.2.x as it is with Quarkus 3.1.x.
Actual behavior
Failed to execute goal io.quarkus:quarkus-maven-plugin:3.2.2.Final:generate-code-tests (default) on project intervention-service: Quarkus code generation phase has failed: Invalid command line:
Caused by: org.apache.maven.shared.utils.cli.CommandLineException: unbalanced quotes
How to Reproduce?
Run a Maven build on the command line with either of the properties below containing a character that needs escaping and the build will fail:
Run the exact same Maven build, but use characters that don't need escaping and the build succeeds.
Output of
uname -a
orver
No response
Output of
java -version
Java version: 17.0.4.1, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-17-jdk-amd64
GraalVM version (if different from Java)
No response
Quarkus version or git rev
Quarkus 3.2.x
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
Additional information
MAVEN 'NATIVE' PROFILE:
PIPELINE BUILD OUTPUT: