Iulian Dragos created SPARK-7841:
------------------------------------
Summary: Spark build should not use lib_managed for dependencies
Key: SPARK-7841
URL: https://issues.apache.org/jira/browse/SPARK-7841
Project: Spark
Issue Type: Bug
Components: Build
Affects Versions: 1.3.1
Reporter: Iulian Dragos
- 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|http://apache-spark-developers-list.1001551.n3.nabble.com/Why-use-quot-lib-managed-quot-for-the-Sbt-build-td12361.html])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
