Enhancement request: Use JAR directories for dependencies about sbt-idea HOT 9 CLOSED

I considered this (and if my memory serves me, I think it was initially like this), but using the classpath computed by SBT, and that classpath may include also other locations and transitive dependencies, it is much easier to get the complete classpath this way.

What would be the main benefits of using jar directories instead of individual jars if SBT is managing dependencies?

from sbt-idea.

OK, you start with a simple project, only few dependencies. You create the IDEA files with your great plugin. Then you start adding more and more dependencies. How would you make them available to IDEA? Manually? Or would you recreate the IDEA files?

from sbt-idea.

I always recreate the files, i.e. run "sbt update; sbt idea" after adding new dependencies to project definition (or pom/ivy files). Idea notices the modification on the fly and offers you the choice of reloading project.

Of course this procedure has the limitation that any other non-plugin-generated idea configuration stored in ipr/iml files is lost when recreating, but I haven't found that to be much of a problem yet (i.e. haven't found any non-plugin-generated configuration worth preserving).

from sbt-idea.

The main thing that I wish I could preserve is having IDEA's git integration set up ... but that only takes 5 seconds to re-do each time.

from sbt-idea.

I use to work "withSources" and configure these in IDEA. Any chance that this plugin will do that for me?

from sbt-idea.

Do you mean sources of dependencies and/or scala library? Plugin should already configure scala library/compiler sources and sources of dependencies declared with "withSources()".

from sbt-idea.

Oh, really? Sweet!

from sbt-idea.

Heiko, if your sources are not configured properly see:

http://github.com/mpeltonen/sbt-idea-plugin/issues#issue/16

from sbt-idea.

Closing this for now. Let's get back to this (using jar directories) with another issue if needed.

from sbt-idea.