Can I get some clarificatioin on this? First, local Ivy jars are versioned, by artifact id and by version #. So, we're talking about gora-0.1.jar here, right? So, your point is, if I'm off gitting and developing on Gora, at any point in time, I can run ant on gora and then it updates my local Ivy repo with a gora-0.1.jar file, right? And your point is, this file is different than the previous gora-0.1.jar file (-N minutes ago), and so thus, Nutch isn't really depending on a stable version, right?
If the above is true, what it suggests to me is that perhaps the process of installing Gora as a local Ivy dependency (independent of Nutch's deps) needs a bit more discipline. I'd say, why not make the Gora Ant build publish a gora-0.1-<some snapshot id aka SVN rev or UUID or whatever>.jar? In that fashion, you could develop on Gora, without fear of changing anything in the way that Nutch depends on it (because the 0.1 version that Nutch depends on could be frozen as is).
I'd also be a fan if the above isn't true or doesn't make sense, of actually just uploading Gora to Maven central – can we try that?
P.S. I'm not trying to be difficult about
NUTCH-873 b/c I was the one who did it. If in the end the consensus is to revert it, no egos here, go ahead. I'm just trying to figure out a solution to the problem that allows us to use Ivy as it should be and to not have to make exceptions. My other thought along these lines is that if we can't wrap our heads around Ivy, or getting to Maven Central in any short amount of time, then what about pulling Gora into Nutch SVN? It's ASLv2 licensed and there is nothing against doing this. From there, there would be a clean path to move to Incubation since the code would already be in Apache SVN anyways...