@propensive Have you considered moving to ScalaTest instead of your own test framework?
-
-
Replying to @JanStette
@JanStette It's a good point. Probably not as much as I should have! It would definitely make some things easier.1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive Yes, lots of useful features + less new stuff to learn for committers.1 reply 0 retweets 1 like -
Replying to @JanStette
@propensive Maybe a more standard multi-module project layout would simplify things too?1 reply 0 retweets 0 likes -
Replying to @JanStette
@JanStette What would that look like? There are about 25 modules, and it is getting a bit hairy, especially managing the SBT build...1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive True. For the libraries that are quite independent, separate repos may be preferable.2 replies 0 retweets 0 likes -
Replying to @JanStette
@JanStette I recently merged different repos into one. They were completely unmanageable. But I still publish multiple binaries...1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive Ah I see! How are they versioned, do they all move in lock-step?1 reply 0 retweets 0 likes -
Replying to @JanStette
@JanStette They do now. Previously, versioning was a nightmare...1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive Cool. Seems this sort of thing would work well: http://www.scala-sbt.org/0.13/tutorial/Multi-Project.html …1 reply 0 retweets 0 likes
@JanStette That looks like a clearer explanation of what @AlistairUSM helped me set up. Maybe with some more understanding I can tidy it up!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.