[SPARK-7841] Spark build should not use lib_managed for dependencies

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.1
• Fix Version/s: 1.6.0
• Component/s: Build
• Labels: easyfix sbt
• Assignee: Josh Rosen
• Reporter: Dragos Dascalita Haut
• Created: 23/May/15 10:45
• Updated: 18/Nov/15 02:08
• Resolved: 10/Nov/15 18:14

Description

• unnecessary duplication (I will have those libraries under ./m2, via maven anyway)
• every time I call make-distribution I lose lib_managed (via mvn clean install) and have to wait to download again all jars next time I use sbt
• Eclipse does not handle relative paths very well (source attachments from lib_managed don’t always work)
• it's not the default configuration. If we stray from defaults I think there should be a clear advantage.

Digging through history, the only reference to `retrieveManaged := true` I found was in f686e3d, from July 2011 ("Initial work on converting build to SBT 0.10.1"). My guess this is purely an accident of porting the build form Sbt 0.7.x and trying to keep the old project layout.

If there are reasons for keeping it, please comment (I didn't get any answers on the dev mailing list)

Issue Links

• is depended upon by: SPARK-11798 Datanucleus jars is missing under lib_managed/jars
• links to: [Github] Pull Request #9575 (JoshRosen)