Can't seemingly use this in scala 2.10

[nbauernfeind]

HBC uses Joauth which is built using scala 2.9.2. I was hoping to try out HBC in a scala 2.10 project...

So, there are only a few options:

1. Drop joauth for an alternative.
2. Cross-release joauth and let users drop the dependency (unfortunately sbt is the best build system to do this and I see it is currently using maven)
3. Shade joauth to hide the scala-ness.

Any chance you guys are interested in either of these options?

[kevinoliver]

Twitter will eventually be moving our scala projects to 2.10. In the meantime, your best bet may be to shade joauth and it's dependencies in your build.

[nbauernfeind]

I'm not familiar with an easy way to do that using maven.

And if I've got to do any work my preference is just to build and manage joauth against 2.10.

But I'm just putting this out there: it does make it harder to even try to adopt any project. For people who don't use Scala at all, all they need are two incompatible dependencies (that they don't even know use Scala under the covers) to have a terrible first impression (of both Scala and the projects that aren't compatible).

Thanks for the quick response.

[kevinoliver]

Yeah, I don't love scala's lack of binary compatibility between versions either. This was definitely a factor in why we chose to write hbc in java. There's always a chance we'd write a version of joauth that is java only.

[kevinoliver]

Pull Request #95 should solve this by removing the transitive scala dependency.

[nbauernfeind]

Thanks for the heads up! If I get a chance I'll give this a shot. I ended up sticking with Twitter4j.