Broken 0.2.0 artifact (no .class files in .jar)

[linasm]

scala-collection-contrib_2.13-0.2.0.jar is missing .class files (it only has .properties file and manifest)

https://repo1.maven.org/maven2/org/scala-lang/modules/scala-collection-contrib_2.13/0.2.0/scala-collection-contrib_2.13-0.2.0.jar

@SethTisue @julienrf

[harpocrates]

Just hit this too...

[mpollmeier]

While we're waiting for a usable artifact I published a jar to my bintray. If anyone else wants to use it:

libraryDependencies += "com.michaelpollmeier" %% "scala-collection-contrib" % "0.2.1"
resolvers += Resolver.bintrayRepo("mpollmeier", "maven")

https://github.com/mpollmeier/scala-collection-contrib/releases/tag/v0.2.1
(I simply ripped out scalajs from the build).

[skradel]

Ditto, the (essentially empty) artifact gave rise to a certain amount of head-scratching; using 0.1.0 for the time being to quiet MultiMap deprecation warnings.

[SethTisue]

this is an OSGi / sbt-osgi problem. it's similar to scala/community-build#981 and scala/scala-parallel-collections#5

[SethTisue]

one thing we might consider here is whether this stuff ought to be under scala.collection (or any other scala. subpackage) at all

[SethTisue]

another possibility is to just disable the OSGi stuff in this repo, and document it as a limitation that we'd welcome community help with but don't plan to tackle ourselves (the core Scala team). Adriaan has already said he's fine with that (and there wasn't any dissent within the team)

I'll poke at sbt-osgi and sbt-scala-module and see what I think that would involve