Are there any pros to add root module in build.sbt? -


i have multi module sbt project:

├── build.sbt ├── bar │   ├── build.sbt │   └── ... ├── foo │   ├── build.sbt │   └── ... └── ... 

and 2 versions of build.sbt:

lazy val foo = project in(file("./foo")) lazy val bar = project in(file("./bar")) 

and second version:

lazy val foo = project in(file("./foo")) lazy val bar = project in(file("./bar"))  lazy val root = project(id = "root",   base = file(".")) aggregate(foo, bar) 

what differences between these versions? there pros in second version?

with second version loaded type projects @ sbt command line , should see have 3 of them. 1 star @ front default project. root project. commands type apply it. aggregate project commands applying in turn both foo , bar.

package example command - typing should produce jar file has both foo , bar classes in it, if want.


Comments

Popular posts from this blog

searchKeyword not working in AngularJS filter -

sequelize.js - Sequelize: sort by enum cases -

user interface - how to replace an ongoing process of image capture from another process call over the same ImageLabel in python's GUI TKinter -