chilly-librarian-83669
12/09/2018, 8:36 PMaloof-angle-91616
12/09/2018, 8:45 PMjvm_binary()
and jvm_app()
which bundle together resources and code, and we do (separately) support publishing to external package repos.
the deployment part is pretty extensible, from my personal (limited) experience -- last week was twitter hackweek and i was able to make it possible to produce a native executable using the graal vm from any jvm_binary()
or jvm_app()
which has zero startup time (i am going to make a pull request today or tomorrow). on a separate angle, the c++ support we've been improving makes it possible to develop e.g. tensorflow custom operators without having to use bazel or control the environment at all, since we provide the compiler and linker with our very slick interface for providing binary tools, which is something that bazel will likely never ever do. so on the end of at least supporting the use of external tools for packaging, i believe pants allows the integration of external tools without having to rewrite the world. i'm not familiar enough with sbt-native-packager
and friends but pants also has fantastic support for integrating jvm tools into tasks (i was able to do the graal native image bit to e.g. run scalafmt), so depending upon the workflow, i suspect you will be able to integrate jvm tools that aren't extremely sbt-specific without a huge amount of difficulty. there is definitely some documentation about the use of jvm tools in tasks but i don't know where it is off the top of my head.chilly-librarian-83669
12/09/2018, 8:50 PMaloof-angle-91616
12/09/2018, 8:51 PMchilly-librarian-83669
12/09/2018, 8:51 PMjvm_binary
or jvm_app
aloof-angle-91616
12/09/2018, 8:52 PMchilly-librarian-83669
12/09/2018, 8:52 PMaloof-angle-91616
12/09/2018, 8:52 PMchilly-librarian-83669
12/09/2018, 8:53 PMaloof-angle-91616
12/09/2018, 8:55 PM