Open ErikThorsell opened 5 years ago
It detects Linux just fine (bin/3.6.0/protoc-3.6.0-linux-x86_64.exe
) but yes it seems the system isn't compatible. It rather looks like https://github.com/os72/protoc-jar/issues/15, missing glibc or so
Any plans on supporting a locally provided protoc, instead of the ones shipped with protoc-jar? This would basically fix the issue of running on Alpine.
Edit: nevermind, you actually already do this and are just missing the documentation for it: https://github.com/os72/protoc-jar-maven-plugin/blob/master/src/main/java/com/github/os72/protocjar/maven/ProtocJarMojo.java#L265
How can I change the protoc command path?
<plugin>
<artifactId>protoc-jar-maven-plugin</artifactId>
<groupId>com.github.os72</groupId>
<configuration>
<protocCommand>protoc</protocCommand>
</configuration>
</plugin>
@contrun does this answer your question? :-)
@michaelkrupp Thanks
Is this maybe related to the download issue I had?
Try to specify the artifact yourself: <pluginArtifact>com.google.protobuf:protoc:${dependency.protobuf.version}</pluginArtifact>
This will force this plugin to do maven resolution instead of trying to download it manually.
@bmhm This is a runtime issue. See os72/protoc-jar#15, missing glibc or so
As a workaround I've found you can add the gcompact
package (apk add gcompat
), which will provide a glibc compatibility layer for Alpine's musl C library.
Perhaps related to https://github.com/os72/protoc-jar-maven-plugin/issues/39.
After downloading plugin (version 3.6.0.1), as part of a pom.xml on a Jenkins agent based on an alpine-image, I get the following error:
Running the exact same project on my local machine (Windows 10) works just fine.
It seems like the plugin thinks it's running on Windows (since it's attempting to execute .exe-files). I have yet to find a workaround that works both in my CI system and locally.