By default sbt test is running all projects in parallel. This leads to problems because the conductr-client-lib projects needs to run sequentially.
This commits adds a falg in the global build.sbt to run the projects sequentially during testing. An alternative would be to use sbt project1/test:test project2/test:test ... instead of sbt test. However, sbt release is using the command sbt test on the root level before releasing a new version. So the latter wouldn't work when releasing new conductr-lib versions. Hence the fix.
By default
sbt test
is running all projects in parallel. This leads to problems because the conductr-client-lib projects needs to run sequentially.This commits adds a falg in the global
build.sbt
to run the projects sequentially during testing. An alternative would be to usesbt project1/test:test project2/test:test ...
instead ofsbt test
. However,sbt release
is using the commandsbt test
on the root level before releasing a new version. So the latter wouldn't work when releasing new conductr-lib versions. Hence the fix.