So, all being well, I'm going to publish Magnolia today, but I have some dependencies to resolve! Is it possible to have two separate SBT projects whose submodules form a DAG, but with dependencies in both directions at the project level?
-
-
My current plan is, for now, to check in an unmanaged jar of the test library (built without the Magnolia bits, which aren't essential anyway).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Shading is the act of renaming your packages via byte code manipulation. sbt-assembly supports it: https://github.com/sbt/sbt-assembly/blob/master/README.md#shading ….
-
Aha, no, I didn't consider that. But the situation shouldn't need it, because my dependencies are acyclic at the fine-grained level. I've gone with checking in pre-built binaries, and everything seems ok so far...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.