These are chat archives for sbt/sbt

29th
Dec 2015
Jaroslaw Rozanski
@jrozanski
Dec 29 2015 16:01
@matanster I would guess (and sorry as I am only guessing) that as you are dealing with two independent projects you might need to use aggregation http://www.scala-sbt.org/0.13/tutorial/Multi-Project.html#Aggregation
matanster
@matanster
Dec 29 2015 16:05
@jrozanski sure I'm quite familiar with aggregations. It has been the detail of elegantly bringing together disparate projects which I had been dealing with. I summarized my experience in http://stackoverflow.com/questions/34503310/how-do-you-compose-sbt-projects-into-a-single-build, in case anyone wishes to comment or it is useful to anyone else, as the task can get a little annoying first times you do that.
Jaroslaw Rozanski
@jrozanski
Dec 29 2015 16:07
@matanster to be honest in your use case I would fallback onto dependsOn with git URI and develop on dependency separately but I understand this not quite what you were strugling with
matanster
@matanster
Dec 29 2015 16:08
mmmm I've never used that, maybe that would be cleaner, how would that flesh out?
would the git uri be a pointer to a directory containing the depended upon project? will sbt just make its up-to-date outputs available to each compilation of the dependent project?
Jaroslaw Rozanski
@jrozanski
Dec 29 2015 16:11
it will checkout project, build it in ~/.sbt/0.13/staging/ and satisfy dependency
that's about it
matanster
@matanster
Dec 29 2015 16:11
Yeah but I hack on both together. So the depended upon project updates frequently
Jaroslaw Rozanski
@jrozanski
Dec 29 2015 16:12
than it is not quite suitable for your workflow
matanster
@matanster
Dec 29 2015 16:12
yeah, anyway good to know I followed in your idea. thanks!