Clever Geek Handbook

Gradual transition from Maven to SBT

Currently our entire project is being built with Maven on Windows. We were unable to make the incrementally compiled code work at runtime (50% of the time it failed with some kind of error), so to benefit from a warm compiler and (perhaps?) A properly working incremental compilation, we are thinking of switching to SBT. However, I currently only have one sprint to work on, and I'm afraid to put all my eggs in one basket and try to move the whole project into a sprint. I need to find a way to make this change gradual so that I can advance one module at a time. So here are the basic questions:

  • How can I include SBT modules in a Maven build (or maybe vice versa with my "parent" in SBT, but part of the modules that are still being built with Maven)?
  • How can we benefit from IDE support (currently IntelliJ 13) like updated change indices in pom / Build.scala, task and target invocations, etc.

Any advice on the topic is much appreciated.

+3


source to share


1 answer


In the end we made the switch and we don't regret it. Writing SBT tasks is easier because it's just Scala. Incremental compilation is now performed (used to fail in Maven s java.lang.InternalError: Enclosing method not found

when deploying to JBoss) and build times are significantly faster. Unfortunately, we didn't find a way to make the gradual transition, so we had to take risks. Incremental compiled jars still don't work, but Typesafe is about to fix this issue in 2.11.6



+2


source






More articles:


All Articles