Update to Akka 2.5, add CI #21
Conversation
.travis.yml
Outdated
| - 2.11.11 | ||
| notifications: | ||
| slack: | ||
| secure: QcJzLxkSVl91qQnHD/DalJN2QuXcb2ac8V/mCb8TkzbB0fVX15o1M9JV8JHnIT0asjiNxrzne5CP/7jfnI3coQIuVkOlBV0gViLI1UO74G0wXij6Z2s+XhCaLfPiwlrE22NoipOtAC6aLMZ0EYbWw6vMCqQuXTi7QDqQKpCOgPks4/wbwi07AvxiBDBPBZXiciw7dkT0WDBM+XxhjvINTvgT9CuaQwSnLLBRwu0JjhVeaBTssx0kB85FyGhyrDq4N/36TsdJJRfGVOH20WXPQ8jqw0Vmnt3TkYaw8QTdIE1s2owio0xmrMkKpaWp/PJ1RQBFHLg7NmgjwOUby0YdYeg11OwhPIx7YfcPHrJon5QNPYc00ti7h4HEg3+vX/uPbi9P7RC/gYYM39p4OhNmfzs9azEMIKHRvz0m7r4QMKgTwUNdpLVm4+BgHk0Y2skNy+Nv5W6bH4Y5FbV/DjiK72XBq5N0s7mH2bM3bhOorUc4keXL5SxNCqbNjW+0cRiMjOxk1r63X7jlxO9UPQMBth6VZ2l+gCz/8iw/CPhXo1Qmzc0P5a8RD+sQVIbKDfrbnufC1AF659CSefrGRRKmUsnhjHexpA6/a5kCjGPYGbt6fgK/BwIi+eRjWP2q5IS1YZhJjG1hxtFXlrMU8WcPkHof42q34dhOgTBMIOsPc6I= |
There was a problem hiding this comment.
Don't know how this works, but should this be committed?
There was a problem hiding this comment.
It says "secure" because it's encrypted with a key connected to our specific repo. It's safe to have it in an open-source repo.
|
|
||
| organization := "net.artsy" | ||
|
|
||
| homepage := Some(url("https://github.com/artsy/atomic-store")) | ||
|
|
||
| licenses +=("MIT", url("https://opensource.org/licenses/MIT")) | ||
|
|
||
| scalaVersion := "2.11.8" | ||
| scalaVersion := "2.11.11" |
There was a problem hiding this comment.
This can definitely wait, but I wonder if we should be cross-building for 2.12 too. It seems pretty simple, but don't really know.
There was a problem hiding this comment.
I can add that to the matrix.
build.sbt
Outdated
| "org.iq80.leveldb" % "leveldb" % "0.7", // For LevelDB journal | ||
| "org.scalatest" %% "scalatest" % "3.0.1" % "test", | ||
| "org.scalacheck" %% "scalacheck" % "1.13.4" % "test", // Property-based testing | ||
| "org.iq80.leveldb" % "leveldb" % "0.9", // For LevelDB journal |
There was a problem hiding this comment.
I wonder if we need this at all. I think we can do without.
There was a problem hiding this comment.
You can decide that. I'm not sure.
There was a problem hiding this comment.
Hmmm....let's remove it. It's a different storage backend than we actually use, and I'm almost positive everything will work just fine without it.
|
Checkmarks! 🙌 |
Since we use TravisCI for a number of our open source projects, I started setting it up. I will test on my branch until I get the automatic pushes to Maven Central.