Dependency on both lightbend and typelevel versions of scala-library

I am trying to bundle an app that depends on freestyle as a single jar using sbt-assembly and i am getting conflicts about duplicate classes from scala-library. The issue seems to come from iota which shows this dependency tree including both versions of the scala-library (the tree is generated using https://github.com/jrudolph/sbt-dependency-graph):

[info] io.frees:freestyle_2.12:0.2.1-SNAPSHOT [S]
[info]   +-com.47deg:iota-core_2.12:0.2.0
[info]   | +-org.typelevel:cats-core_2.12:0.9.0
[info]   | | +-com.github.mpilquist:simulacrum_2.12:0.10.0
[info]   | | | +-org.scala-lang:scala-library:2.12.2
[info]   | | | +-org.typelevel:macro-compat_2.12:1.1.1
[info]   | | |   +-org.scala-lang:scala-library:2.12.2
...
[info]   | +-org.typelevel:scala-library:2.12.1
...

I have searched this repo and the only reference to typelevel seems to be in the scalaOrganization at file https://github.com/47deg/iota/blob/master/project/ProjectPlugin.scala which may also explain why i am getting org.scala-lang:scala-library in version 2.12.2 and org.typelevel:scala-library in version 2.12.1. It seems that the scalaOrganization defined as typelevel or some other sbt configuration may be causing the problem. Ideally since most projects will already include org.scala-lang:scala-library anyway it may be better if no dependency on the typelevel version existed although i am not sure about the implications of this.

[andyscott]

I finally got a fix together. Awaiting review and merge of #63.

[andyscott]

Sure thing. It wound up being substantially more complicated originally anticipated due to a slew of SBT plugins and the need for cross building across different Scala versions.