Publish signed universal artifcts to Maven Central with POM.

[mmacfadden]

Expected behaviour

We are currently deploying to maven central at oss.sonatype.org. They require signing published artifacts. For our normal artifacts we are using sbt-gpg to sign and publish.

We use sbt-native-packager to create our binary distributions and we generally us universal:publish to push to a repo. I am wondering if there is a way to publish signed artifacts either using sbt-native-packager, stb-gpg or a combination of both. Following this stack overflow article: Publish zip created by sbt-native-packager . We can get signed artifacts. But they they show up under com/example/my-artifact_12.2/1.0.0 instead of com/example/my-artifac/1.0.0 like they do now. This may be ok, if it is the best solution.

I also noticed that when publishing them on their own, like we did before. There was no pom file in the com/example/my-artifac/1.0.0.

Any tips would be greatly appreciated.

We posted this also on Stack Overflow here: https://stackoverflow.com/questions/59621005/how-publish-signed-artifacts-using-universalpublish-in-sbt-native-packager

Actual behaviour

We haven't been able to figure this out. :-). thanks for the great work on this project thought!

Information

• What sbt-native-packager are you using: latest.
• What sbt version: 1.3.5
• What is your build system:Linux and MacOS
• What package are you building: Universal
• What version has your build tool: N/A
• What is your target system: N/A

[muuki88]

Thanks @mmacfadden for your feature request.

The publishing part is out of scope for native packager. If you want maven POMs in your artifact this is something sbt packager will not care of.

We have some signing support, but that wasn't touched in ages. RPM and debian have something IIRC, but not sure about the universal support. I'm very happy to merge an pull requests here :heart: