Forwarding an issue one of our devs is having as we're trying to productionize our use of the videobridge, he's written up the report below:
We would like to treat jitsi-videobridge as a library instead of a running application, due to our service layer shared by all services within our datacenter. Notably, we would like to wrap the main so that we can provide unified logging (elastic search) and wire in our metrics libraries, for example.
However, the current "maven time based snapshotting" is incompatible with our java build system (we use SBT + Coursier [https://github.com/alexarchambault/coursier]). Generally speaking, SBT uses Ivy for dependency management, and while there is quite good support for maven time-based snapshotting (which is what it appears you're currently using), it is limited - and the current repository layout does not work
In addition, we would like to be able to reliably pull an exact snapshot version when we're ready to upgrade, for example, and the current "1.0-SNAPSHOT" of jitsi-videobridge doesn't facilitate this.
Is there any chance you could move to a more standardized/ivy/coursier compatible snapshot versioning? Maybe something that uses the output of "git describe --tags --always" (this happens to be how we version everything, and it has a lot of advantages - you can very quickly know exactly what revision a jar is from).
Finally, there are a few dependencies that are missing version numbers, which is generally required by ivy/coursier and generally a good practice in my opinion.
We have filed and/or are tracking some issues within Coursier that should address most of this, but they are likely not going to be addressed any time soon:
https://github.com/alexarchambault/coursier/issues/209 - support for latest.version
https://github.com/alexarchambault/coursier/issues/157 - unable to resolve dependencies when no version is specified.
https://github.com/alexarchambault/coursier/issues/169 - support for maven time based snapshotting.
I've included the error log of fetching with coursier below.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: