Git contained in the Maven image suggested by OneDev (3.6.1-jdk-8) is pretty old. You may specify the image as "maven:3.8.4-jdk-8" to work around the issue. OneDev job suggestion will also be updated to use this image.

State changed as code fixing the issue is committed

State changed as build #2249 is successful

Sorry to bump the issue but I think it's somewhat related - is there a way to globally set default image for maven builds (and definition created by 1dev)? I see in the script image: '@script:builtin:maven:determine-docker-image@' so I could probably replace the image with maven:3-eclipse-temurin-17 but doing that for each project doesn't seem like a good idea. And the original entry suggests there is a script and some sort of logic being applied to "determine docker image" so my question is - how we can affect/configure it?

You may write a custom script returning desired image, something like @script:get-maven-image for the image field. But still you need to change all maven step to use that script for the first time.

Any hint how to / where to create such custom script? I checked the documentation / tutorials / blog on medium and sub-sections in build category and haven't found mentions/notion of "scripts". I'm still setting up our 1dev and it would be ideal to have one "template" that would be flexible and configurable via variables/external (global) scripts and use it for all subsequently imported projects that would save a lot of work in the future.

(I'm also trying to figure out how to handle deploying maven artifacts to maven repository but that's a separate issue though :-) )

Custom script can be defined here:

For instance, you may define a script named maven-version, with content set to

return "3.8.2"

Then you can reference this script in build spec via @script:maven-version@