"Rapture could easily be the Guava of Scala" "Rapture is a zero-user library" My thoughts on how to reconcile these: http://rapture.io/blog/rapture-manifesto …
-
-
Replying to @propensive
@propensive Have you considered moving to ScalaTest instead of your own test framework?1 reply 0 retweets 1 like -
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
@JanStette But as things currently stand, there's far too much copy/pasting in build.sbt. I'm sure it could be half the size...
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.