I gave Raven a quick once over tonight. This is in no way a thorough examination. but here are some concerns I have so far:
- Eclipse support is a little sketchy compared to Maven. You can run a lib_dir task and then configure Eclipse to use the distribution jars, but then you’re not really pointing at a single repository. Of course, the Raven repository stores gems, not jars, so this may be the best we can hope for right now.
- Absent is a clearly documented way to install a jar that isn’t in the Maven repository already, or being built by Raven. To be fair, this is a pain in the ass in Maven, also.
- `raven repository jruby` didn’t do anything and didn’t bother to tell me what it wasn’t doing or why it wasn’t doing it. So I had no idea if there was something I needed to be doing to make it work.
Raven is a cool idea. I like gems and the Java attempts at building a unified build tool have been, at best, clumsy. On merit of the idea alone, I think I’ll try Raven on one or two personal projects, just to see how it holds up.