-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement request: Use JAR directories for dependencies #7
Comments
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? |
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? |
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). |
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. |
I use to work "withSources" and configure these in IDEA. Any chance that this plugin will do that for me? |
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()". |
Oh, really? Sweet! |
Heiko, if your sources are not configured properly see: |
Closing this for now. Let's get back to this (using jar directories) with another issue if needed. |
Currently for each JAR from lib_managed a dependency of its own is created. It would be nice to have (optional at least) lib_managed//compile, .../test, etc. as JAR directories.
The text was updated successfully, but these errors were encountered: