Community build

Todo List:

• Infrastructure for community build : @olafurpg
• ScalaCheck : @allanrenucci (stuck on this assertion error in typer.Implicits)
• ScalaTest : @olafurpg
• Squants : @olafurpg
• Algebra : @olafurpg
• json4s : @liufengyun (fixed: #2218 #2250 #2239)
• twitter/util: @liufengyun
• scopt/scopt: @allanrenucci
• Better-Files : @allanrenucci
• paiges
• scalariform
• scala-parser-combinators
• scala-xml
• jardiff
• sbinary
• log4s (note: scala-reflect macros can be replaced with inline def https://github.com/Log4s/log4s/blob/1155339023744cb6d2f9809cfff8ea5b57c59868/src/main/scala/org/log4s/Logger.scala#L88-L101)
• http4s/blaze (note: depends on log4s)

Repo: https://github.com/lampepfl/dotty-community-build

[felixmulder]

Keeping it on staging is fine IMO, but the other point I don’t agree with.

I propose the structure to be something like:

.
├── dotty (submodule @ latest master)
├── better-files (submodule)
└── scalatest (submodule)

Then you do publishLocal on dotty and use it to compile the other submodules.

Making a fork of dotty which contains submodules sounds messy.

[smarter]

I don’t think porting Scala 2.9 code is going to be very useful. Ideally we want to compile libraries with their dependencies, so we need recent version of these dependencies. What we need is to figure out how to replace macros in projects on case by case basis, even if this means adding special cases in the compiler to ease transition (e.g. support for kind-projector syntax)