-
Notifications
You must be signed in to change notification settings - Fork 423
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
eclipse-temurin images have no gpg binaries #256
Comments
the images have the bare minimum, some images don't even have git |
Could it be codified what binaries come standard on the image? Some have git and some don't, and consistency, in either direction, would be super nice to have. Thanks! |
right now they have what comes from the parent images and it is tested under I'm not keen on installing extra packages as that could open a can of worms |
Does this mean that all images will have this minimal baseline of packages, or will the tests be tailored to each upstream? Thanks! |
tests are tailored to each upstream |
Hi,
Moving the build pipeline usage from maven:3.8-openjdk-17 to maven:3.8-eclipse-temurin-17 makes open source projects failing.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign (sign-artifacts) on project futurefit: Unable to execute gpg command: Error while executing process. Cannot run program "/usr/bin/gpg": error=2, No such file or directory -> [Help 1]
This is at gpg signing time before deploying to maven central.
Since gpg is a standard tool for signing maven artifacts, shouldn't it be included to maven eclipse-temurin images like maven:3.8-openjdk-17 ?
Regards,
The text was updated successfully, but these errors were encountered: