scala - Cross-cutting "logical" scopes in multi-project sbt builds -
scala - Cross-cutting "logical" scopes in multi-project sbt builds -
let's have build handful of subprojects related have logical classification above sorts of things build aware of.
for example, might have collection of subprojects
foo bar baz quux woof oinki know woof , bar part of i'd phone call server component. baz mutual dependency of both, , foo, quux, , oink on client side. whole build aggregate of various subprojects, i'd "focus" on server side, or client side, or whatever.
on 1 hand, i've considered nested aggregated projects, i'm not sure how works sbt's other functionality.
on other, thinking of making custom scopes cutting across subprojects. i'd able configure related projects similar keys, handy able i'd update key grouping of related projects.
what's approach sort of thing? thinking wrong?
dealt similar situation.
my solution break things out sub-projects in sbt, , utilize dependson link sub-projects. nice unintended consequence here sub-projects dependson mimic maven dependencies perfectly. if publish 1 of these, magically have maven dependencies others. tools eclipse , intelli see these dependency chains rather easily.
this gives alternative of keeping things in same sbt project or not, no difference in end. tie @ 'maven-style' dependency. using local maven repo here or remote 1 works great. @ point, you're free create selection based on code-management , not dep-management, whether or not break things different sbt projects.
edit: in end, if want move module out of multi-project sbt thing, need add together regular maven deps whatever code base of operations requesting other
scala sbt
Comments
Post a Comment