JARs exported from modules should not be duplicated as dependency of dependent module

[retronym]

SBT doesn't really do this part correctly, see http://code.google.com/p/simple-build-tool/issues/detail?id=44

But the plugin could work around this by omitting jars as a direct dependency of module A, if that jar was exported by a module B, where A depends on B.

Alternatively, JAR dependencies could be marks as not 'exported' in the IntelliJ config.

Having the same jar repeated on the classpath leads to annoyances like this error with SLF4J:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/E:/code/analytics/analytics-test-support/lib_managed/scala_2.8.1/compile/logback-classic-0.9.24.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/E:/code/analytics/analytics-utils/lib_managed/scala_2.8.1/compile/logback-classic-0.9.24.jar!/org/slf4j/impl/StaticLoggerBinder.class]

[ijuma]

It would certainly be nice if we removed duplicated jars. It would make IDEA indexing faster, reduce memory usage and avoid the issue where there are many duplicates in the Open Class dialog.

You make a good point that we can possibly fix this without having to wait for SBT 0.9.x.

[jrudolph]

I tried to fix it. See pull request in issue #46.

[ijuma]

Nice. :)

[mpeltonen]

Fix merged. Thanks!

[ijuma]

I filed issue #48 for a similar thing to be done with the scala library. Johannes, do you want to tackle that too? :)