Nils Breunese

We prefer using `frontend-maven-plugin` over `exec-maven-plugin`, because via `frontend-maven-plugin` we can manage default (LTS) versions for NodeJS and Yarn for our teams, and if they need to deviate they can...

The issue is that a yarn binary that is built to be used with glibc doesn't work on Alpine out of the box, because Alpine uses musl instead of glibc...

frontend-maven-plugin downloads a musl-based NodeJS since https://github.com/eirslett/frontend-maven-plugin/pull/853, so there should no longer be a need to install glibc (which adds quite a bit of disk usage to that otherwise tiny...

Another data point: I have various flavours of JDK 8, 11 and 15 installed on macOS 10.15.6: ``` % /usr/libexec/java_home -V Matching Java Virtual Machines (7): 15, x86_64: "OpenJDK 15"...

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.

I think this issue is a duplicate of https://github.com/AdoptOpenJDK/TSC/issues/33

> Why not using protobuf statically compiled? It would work regardless of glibc or musl being the libc! I guess that would solve this issue, yes. > Other thing I...

I also ran into the issue of the downloaded `protoc` not working on Alpine Linux. @os72 Could protoc-jar add a statically compiled `protoc` binary for Linux which would work on...

I just found that if you install the `gcompat` package ("The GNU C Library compatibility layer for musl") on Alpine, then the binary from Google does work. Without `gcompat` it...

According to https://golb.hplar.ch/2017/10/JCE-policy-changes-in-Java-SE-8u151-and-8u152.html unlimited strength can enabled by a single line of code without any additional downloads: ``` Security.setProperty("crypto.policy", "unlimited"); ``` Alternatively you can also uncomment `#crypto.policy=unlimited` in `/lib/security/java.security`. Since...