scala - Can someone please explain the right way to use SBT? -

I'm getting out of the closet on it! I do not understand the SBT there, I said, now please help me.

All roads go to Rome, and it is similar to SBT: SBT to get started with SBT There are different ways to add and fix on the SBT launcher , SBT-extras , etc., and then on the repository. What is a 'best' way?

I am asking because sometimes I lose a bit SBT documentation is very complete and complete, but I do not know that build.sbt Or when to use project / build.properties or project / Build.scala or project / plugins.sbt .

Then it gets fun, Scala-IDE and SBT - What is the correct way to use them together? First of all, what comes the chicken or egg?

Perhaps the most important thing is that you have the right properties and versions to include in your project? Do I get out of Macbetha and start to open my way up? I am getting projects that are quite a lot, which include everything and kitchen sinks, and then I know - I am not the only one who gets lost.

As a simple example, right now, I am starting a new project I want to use the latest features of slick and scala And possibly the latest version of SBT will be needed What is the sensible point to get started, and why? In what file should I define it and how should I view it? I know I can do this work, but I would really like an expert opinion, where everything should go (why the bonus should go).

I have now used SBT and then SBT Extras for more than one year for small projects. As some of these headaches magically disappeared), but I'm not sure why I should use one or the other, I can not understand how things fit together ( SBT and repositories), and thinks that the next person is very much like this Having trouble if it can be explained in human terms.

Most importantly, how can you find the right treasure? And version to include in your project? Do I just pull Macbeta and start moving forward? For Scala-based dependencies, I often find projects that include everything and kitchen sinks

for example: signal to use:

  libraryDependencies + = "org.scalaz" %% "scales-core"% "6.0.4"   
 or where are the instructions:  < Pre>  addSbtPlugin ("com.typesafe.sbteclipse"% "sbteclipse-plugin"% "2.1.0-RC1")   
 For Java-based dependencies, I see it For what I mean there, click on the SBT tab. For example, the signal to use:  
  libraryDependencies + = "net.sf.opencsv"% "opencsv"% "2.3"   
 Then out the machette Start pulling and hacking your way forward. If you are lucky then you do not use jars, which depends on a few jars, but with incompatible versions. Given the Java ecosystem, you often end up with everything and kitchen sinks and try to eliminate dependence or to ensure that you are not losing the necessary dependencies.  
 
  As a simple example, now, I am starting a new project, I want to use the latest features of SLICK and Scala and possibly need the latest version of SBT What is the sensible point to begin, and why?        
 
 
 
  
 
  {& lt; Build-uri & gt;} & lt; Project-id & gt; / Config: key (for task-key))   
 3 flavors ( SettingKey ,  TaskKey ,  InputKey ) - Read the section "Task Keys" in   
 Keep those 4 pages open all the time so you can jump and see different definitions and examples:  < 
 
 
 
 
 
 
 
 
 
   
  show  and  Observe the maximum of  to get familiar with the actual values ​​of settings, their dependencies, definitions and related settings.  for the tab closing . I do not believe that the relationships you search for, are documenting anywhere on the  inspection . If there is a better way, then I have to know about it.