The current publish process is very convoluted and error-prone. It involves grabbing the packaged jars containing native libs, signing them manually, then stuffing them into a local "staging" repository one by one before pushing them out to the Nexus staging repo.
Since the native libraries likely won't change anywhere near as often as jvm-brotli code, it would make more sense to simply move the pre-compiled libraries inside their corresponding natives folder and have maven copy them into the classpath when the release profile is run.
This way, the release could be done by maven as a single operation, and the artifacts would be signed automatically. This would drastically cut down on release complexity
The current publish process is very convoluted and error-prone. It involves grabbing the packaged jars containing native libs, signing them manually, then stuffing them into a local "staging" repository one by one before pushing them out to the Nexus staging repo.
Since the native libraries likely won't change anywhere near as often as jvm-brotli code, it would make more sense to simply move the pre-compiled libraries inside their corresponding natives folder and have maven copy them into the classpath when the release profile is run.
This way, the release could be done by maven as a single operation, and the artifacts would be signed automatically. This would drastically cut down on release complexity