My story [skip for the real answer]
I have become increasingly intrigued with the functional programming paradigm and its implementation in Scala. I’m thoroughly enjoying working my way through Scala creator Martin Odersky’s coursera course which I highly recommend to anyone from “timid and interested” to “hardcore.” As a data scientist with a statistics and economics background, I code every day in languages like R and Python wrangling data, implementing machine learning algorithms, tapping APIs and building data tools for data scientists. However, I don’t build [professional-grade] software. Ive never taken a formal computer science course in college/grad school or learned Java. Admittedly, I’ve felt overwhelmed at times by so many new concepts and tools with the course. I’m simultaneously figuring out Scala, Java, sbt, eclipse, functional and object oriented paradigms.
As a learner poking my head in the field, I find it refreshing reading stories from fellow newcomers battling similar problems, even if they appear trivial in hindsight. I also find it most effective teaching material when you still remember how you learned it. Thus, this post and [likely, yet currently unwritten] subsequent Scala posts will be experimental learning notes rather than wisdom and tested best practices.
Managed vs Unmanaged dependencies
One of the stumbling blocks I encountered on my first Scala project was a simple one: working with external libraries with sbt and Eclipse. I started using unmanaged dependencies (downloading some jar files and pointing Eclipse to them) which worked well, until I encountered a library which had further dependencies – I was working with json4s. More on unmanaged vs managed dependencies here. Managed dependencies have the advantage of being, well, managed. You simply specify a library with a version and Ivy (a tool similar to Maven) will go out on the web and download it along with any dependencies.
My issue was I initially couldn’t get Eclipse to actually go out and download my dependencies. As evidenced by this StackOverflow post, there are probably many ways to achieve this. The piece I was missing was using sbt in the Terminal while Eclipse was running to actually download the libraries.
Make Eclipse recognize managed dependencies
Here’s a step-by-step process
Step 1: Create a build.sbt file
Create build.sbt in the root project directory. For example, my build.sbt looks like this:
Step 2: Open the Terminal
Assuming you’re on mac, type the following in the Terminal:
You should see a bunch of jar files downloading… something like this:
Step 3: Refresh project in Eclipse
Now in Eclipse refresh your project by clicking F5, or right click on the project in the Package Explorer tab and click “Refresh”
Step 4: Check that it worked
Now to check that libraries have downloaded and Eclipse has recognized them.
In Eclipse, right click on the project in the Package Explorer tab
=> click “Build Path”
=> click “Configure Build Path”
=> click “Libraries” (icon with a stack of books)
Here you should see the libraries from build.sbt and all their dependencies. Now you should be good to go – import what you need from these libraries in your Scala code.
I configured my environment as recommended by the Functional Programming Principles in Scala course:
- Mac - OSX Yosemite 10.10
- Scala IDE build of Eclipse SDK 4.2.0
- sbt 0.13.9