>>=

How do you test jdk compatibility? It's easy to depend on a new method / class? 30 jars!!!???! Do you have any idea how long SBT will take to resolve...

You could just use `optional` dependencies and let the user pull in the bits they need. The overhead of resolving 30 jars in sbt / ivy is orders of magnitude...

JDK testing I mean you could easily use a class or method from Java 7 and you'll never catch it until you get a bug report, unless you run your...

LOL, yes, definitely... I must admit this does seem like a minefield and even if you had no transitives that is likely to destroy sbt / ivy.

We need random access as well in ensime, and a general URL scheme so that we can basically go from String => Handle, where the string may be a file...

cool! I'm happy to chat through it in the evening sometime. Two major lessons from VFS on how **not** to do it: 1. don't ever leave a file handler open....

btw, if you want to see the ENSIME use cases (both jars and zips) I'd be happy to do a code walkthrough. Streaming access of the entry names as well...

I'm not sure what's in the metadata, but from our perspective we only care about the entry name and (optionally) the content. Don't care about dates or anything.

it is possible that #43 will fix this, if these editors use Emacs formatted `TAGS`

happy to help you write this! My talk at Scala eXchange last week should make this real easy. I predict you could do the whole thing in about 50 lines...