aah, that makes sense.
Remember that the release manager is carrying his/her own
build.properties, and if you build from source, you should too.
in there you override any properties needed. That is why all binary
builds are correct, but your build isn't.
what you are asking for is that we update build.properties.default
before tagging a release, correct?
Filip
William L. Thomson Jr. wrote:
Filip,
On Wed, 2007-05-23 at 18:37 +0200, Filip Hanik - Dev Lists wrote:
hey William, what are you referring to? any specific .java files that
need a version number?
Sorry should have been more specific, the problem lies in
build.properties.default
I was under the impression that we only tag each build, and then there
is a small sucker in a property file that we swap out.
It's the prop file being neglected :)
ie, when you start 5.5.23 then you see
May 23, 2007 6:35:55 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
Not here, with 6.0.13 I get
May 23, 2007 1:15:58 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0-snapshot
With 5.5.23, I get
May 23, 2007 1:17:01 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5
Not sure what that's about with 5.5.23, since the prop file has 5.5.20,
so should reflect that version but does not.
404, and other error pages also reflect the versions as shown in the log
file and prop file.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
