You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently multijvm just does a straight copy of jars from the classpath list to the jars directory. The problem with this is that when the classpath changes, any jars that shouldn't be there are left there. In a project where dependencies are changing frequently, this leads to frequent unpredictable LinkageErrors, unless you ensure you do a clean before each test run, which slows everything down.
sbt.Sync will both speed things up because it will avoid unnecessary copying, and it will ensure the classpath is correct even when the classpath changes, avoiding spurious LinkageErrors.
The text was updated successfully, but these errors were encountered:
Currently multijvm just does a straight copy of jars from the classpath list to the jars directory. The problem with this is that when the classpath changes, any jars that shouldn't be there are left there. In a project where dependencies are changing frequently, this leads to frequent unpredictable
LinkageErrors
, unless you ensure you do a clean before each test run, which slows everything down.sbt.Sync
will both speed things up because it will avoid unnecessary copying, and it will ensure the classpath is correct even when the classpath changes, avoiding spurious LinkageErrors.The text was updated successfully, but these errors were encountered: