These are chat archives for sbt/sbt

26th
Mar 2016
matanster
@matanster
Mar 26 2016 00:12
Well resorting to MergeStrategy.first for the packages introducing classes in conflict works for me. I think it's just typical java dependency hell, not specific to sbt.
excluding the dependencies that bring along the conflicting classes should be better (safer) because disposing only the conflicting class files ― probably means ending up with mixed versions of the conflicting dependencies.
matanster
@matanster
Mar 26 2016 00:21
@dwijnand thanks for your support
OlegYch
@OlegYch
Mar 26 2016 00:21
dwijnand it is a regular question on freenode
Joseph Earl
@josephearl
Mar 26 2016 01:11

I'm having an issue trying to convert the findbugs4sbt plugin to an AutoPlugin, wondering if someone can help.

My initial attempt is here: https://github.com/JosephEarl/findbugs4sbt/tree/feature/sbt-autoplugin

See the findbugs-auto test to reproduce, the test fails with:

java.lang.IllegalArgumentException: Cannot add dependency 'com.google.code.findbugs#findbugs;3.0.0' to configuration 'findbugs' of module de.johoop#findbugs-auto_2.10;1.4.2-SNAPSHOT because this configuration doesn't exist!

The difference between that and the original findbugs test is that original test calls findbugsSettings which adds the ivyConfiguration setting before projectSettings is run.

Joseph Earl
@josephearl
Mar 26 2016 01:29
Solved my issue, needed override def projectConfigurations: Seq[Configuration] for the auto plugin