Hi all: As Peter asked me to, I’ve modified the trunk version to download the compile dependencies at compile time using Apache Ivy, so we won’t be shipping binaries in the source distribution. I’ve hit a couple of minor delays, and I’d like input on how to proceed…
1 - API signature verification using animal-sniffer: The animal-sniffer package is available through Maven Central, so there’s no problem downloading it at compile time, but I’ve had difficulty getting the actual signatures. They’re on Maven Central, but so far I’m having difficulty actually downloading them with Ivy. I think the issue is that the signatures are not actually listed as the artifact in the pom file. From what I can tell, the animal-sniffer plugin does some kind of magic to actually retrieve the signatures. I suspect that I need to dig in to Ivy a little deeper to figure out how to do the same thing. Long term, we should not have a problem. 2 - There are tests in the ‘test’ folder that depend on the ‘imunit.jar’ unit test library from the University of Illinois. Unfortunately this library is not available on Maven Central. I’m inclined to simply disable/comment out both the signature verification and the affected unit tests for now, so as not to delay the release. As I said, the signature issue is probably an Ivy configuration thing. The imunit issue is more of a problem. What I propose to do is contact the authors and see if they’re able to put it up on Maven Central, so we can download it at compile time. If they’re not able to do that, the license would allow me to put it on Central under my own name (much like Stephen Connolly did with the high-scale-lib). Either option will likely take a few weeks. In the mean time, we know that Peter has run both the unit tests and the signature verification locally, so I don’t think there’s a real blocker for the release if we just forgo these tests for now. We’ll re-enable them as soon as possible. Happy to hear any opinions… Greg Trasuk
