---- On Wed, 24 Aug 2016 17:16:35 +0200 Lee Sanders <
hlees...@gmail.com> wrote ----
> Hey, our Eclipse .classpath references jar files that are replaced by a command-line build when dependencies change as part of executing that build. With Java this worked fine and we would just Refresh the Java project to pick up the changed dependencies. Now adding Scala builder and Scala nature to that project the command-line build fails as the jar files seemed to be kept in use in memory and the jar files cannot be replaced because of that. I don't want to close the project to do a rebuild.
>
> Is this expected behavior? A limitation or requirement of keeping file handles to those jars open constantly?
There shouldn't be a need to keep JAR files open - the question now is where this happens because I don't think that we keep JAR files open knowingly.