Lib canton opensource not on a public maven repository

Questions
1

Hi,
Would’t it make sense that the lib canton-open-source-x.y.x.jar be accessible from a public maven repository?
best

2

Could you explain why you’d prefer to get it from Maven? We generally opt for using GH releases for standalone JARs & tarballs and use Maven only for libraries.

3

You want to automate the provisioning of the jar using the standard location and download mechanism that are maven repositories and the use of tools such as maven or gradle to do this.

4

Maven and Gradle are build tools; they’re great for getting build dependencies, but we don’t consider self-contained executable JARs as dependencies: they’re really just executables that happen to be written in Java(ish). Therefore, it’s a bit difficult for me to understand the benefit there could be to fetching them with Maven — having an executable binary buried deep somewhere under ~/.m2 is not as useful as having it plainly available under ~/bin or the like.

This is also why Canton is presented as a tarball, not as a plain JAR file.

Could you elaborate a bit on the use-case you have for fetching the Canton JAR from Maven? Specifically, are you somehow using it as a build dependency?

5

I can understand the request to more easily build / provision components. However, the Daml 2.0 solution stack has more components than Canton and they are all dependent upon each other. So, having Canton’s open source jar available from a public repository would mean managing all of those other dependencies as well. Otherwise different versions of components could be deployed and this is something that we want to avoid. For the moment, we will continue with our current approach.

Thanks for the request.