If you build from sources, it automatically assumes a dev version (you could
have changed it). If you want to override the automatically set version (as
we do it during build), use ant -Dversion=2.9.1
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail:
OK. I just downloaded the 2.9.0 sources from
http://mirror.candidhosting.com/pub/apache/lucene/java/lucene-2.9.0-src.zipto
a clean directory. 'ant jar-core' produced:
'build/lucene-core-2.9.jar'
(no -dev version suffix and I changed nothing). Are you saying that it
should have produced
The build/release formula is always in flux - we likely hard coded the
change in 2.9.0 when releasing - we likely won't again in the future.
Some discussion about it came up recently on the list.
--
- Mark
http://www.lucidimagination.com
Peter Keegan wrote:
OK. I just downloaded the 2.9.0
The -dev version is confusing when it's the target of a build from an
official release.
A build with patches from an official release might warrant a '-dev'
version, I suppose.
(just my 2 cents.)
Peter
On Mon, Nov 9, 2009 at 7:57 PM, Mark Miller markrmil...@gmail.com wrote:
The build/release
Yeah - its a debatable point. You can have issues when building though -
did you build with java 1.5? Then its not like the official build. This
keeps you from confusing yourself about what artifacts are what. You can
override it, but this way you know what you have done. Just because you
have the
I get your points (btw, I built with 1.6), and I like the easy override.
But, my build of 2.9.0 didn't produce a dev jar, which is inconsistent with
2.9.1. I guess that's the flux you referred to.
Peter
On Mon, Nov 9, 2009 at 8:13 PM, Mark Miller markrmil...@gmail.com wrote:
Yeah - its a
Right - I followed the release wiki and took it out for 2.9.0 - but then
before 2.9.1 some discussion arose about not taking it out.
Peter Keegan wrote:
I get your points (btw, I built with 1.6), and I like the easy override.
But, my build of 2.9.0 didn't produce a dev jar, which is
