-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breaks Quarkus maven package and native image generation in docker #175
Comments
Let me know if you need additional information @McFoggy |
Seems like something with Quarkus maven plugin doesn't work correctly with jgitver
|
Closing the issue as I have found a work around, instead of using the 2 Stage Dockerfile to build the native image, I used the default 1 Stage Dockerfile like so
and build the native image in the previous step, using the built-in quarkus docker orchestrator
I'm not 100% sure what's causing the issue, but it's somewhere on the first stage of the |
Issue
version: 1.9.0
usage context:
mvn package
& building a native image through docker)Problem description:
The following github action fails when jgitver is enabled, otherwise, everything builds without any issue, the following playground git repository is generated through quarkus.io starter website vanilla without modifications except the Dockerfile
Based on logs jgitver tries to replace a plugin version in quarkus bom (similar errors/issue with Problem with extension plugins #90, Add default exclude / warning for ".m2" and/or "repository" #91)
Github action: https://github.com/vincejv/playground/actions/runs/3257146900/jobs/5348228766
The following
Dockerfile
was usedI've gone through issue #90 & #91 since the errors are similar, but don't think that this is the issue, as on my jgitver config I've excluded m2 (even though unnecessary) as when I ran
ls -alh
andmvn --version
, the MLR is in~/.m2
See the following logs for
ls -alh
andmvnw --version
jgitver.config.xml
Let me know if you need further information
The text was updated successfully, but these errors were encountered: