we can unfork coursier-using projects now (if version is new enough)

[SethTisue]

we have a number of projects that we had to fork because they are using coursier. it would be nice if we didn't have to fork for that reason — it has now become (I think) the most common reason we have to fork

perhaps some fix is needed in dbuild, or in coursier? or can we configure our way around whatever the problem is?

[SethTisue]

I don't think we have recently tried to see if the problem persists with the latest coursier release

and I also don't think we have made any effort to find out what's going wrong, exactly, and where a fix might be needed

[SethTisue]

https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/2189/consoleFull is an experiment re-adding coursier to an arbitrarily chosen project, namely case-app (chosen because it has few dependencies)

the coursier version used is the latest release, 1.0.0-RC13

[SethTisue]

well color me surprised but also tickle me pink: [info] Project case-app----------------: SUCCESS (project rebuilt ok)

[SethTisue]

let's try fs2 next: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/2191/consoleFull

[SethTisue]

fs2 worked, the failure was in some downstream project, since I pulled in some newer changes in addition to the coursier reinstatement.

so this is looking good, I'll just need to chip away it one project at a time

fyi @alexarchambault

[SethTisue]

I think there are no remaining projects that we have forked only because of coursier. So I'm going to close this, and just keep in mind that we should keep an eye out for further unforking opportunities.