Steven Parkes (JIRA) wrote:
Hmmm ... I've been wondering about this. Turns out that both the svn tag lucene_2_0_0 and the 2.0.0 src tar ball have "2.0.1-dev" in common-build.xml. I don't know if this was intentional, so that the someone using the signed binary tar ball would be clearly distinguishable from something that someone had built? Wouldint think so, but I'm not too up on ASF release procedures.
That's the convention we've used in Lucene projects. The idea is that users should have to go out of their way to build something named lucene-2.0.0.jar, since they're likely to patch things. Only the official builds should look like official builds, everything else should look like a developer build of some version subsequent to the release build.
Yes, this confuses a lot of folks and probably deserves an FAQ. Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
