./sbt clean coverage test
./sbt coverageReport
./sbt coverageAggregate
There is no need to do a full dev cycle (publish to bintray and bump the version in the other project)
each time something changes. For this use case you can benefit from SNAPSHOT releases. Set the version to
version := "0.2.1-SNAPSHOT", and then do a
./sbt publishLocal
in the other project, enable resolving vom local caches by adding a resolver Resolver.mavenLocal and also
switch to the same SNAPSHOT version.
Publishing Versions is done by commiting to master. CI Jenkins will take care of the rest for you.
(!) Bump the version in file build.sbt, otherwise you will get an error when publishing a version that already exists.
We are using the bintray sbt plugin.
You will need a bintray account. Log in through sbt:
./activator bintrayChangeCredentials
Then you can publish new releases with:
./sbt publish