problem building 5.5.15

2006-02-13 Thread Eric Lenio
All -

Apologies in advance if this should go to tomcat-users but I'm
suspecting a problem with the way the source code is being distributed
so I'm starting here.

I downloaded the source file for 5.5.15 and built it.  After installing
it I ran bin/version.sh which said I had version 5.5.0.0.  Not what I
was expecting.

So I followed instructions, exactly, from
http://tomcat.apache.org/tomcat-5.5-doc/building.html to build directly
from subversion.  The build went
fine.  But version.sh still says 5.5.0.0.  I was expecting to have
5.5.15.

So, did I really just build 5.5.0.0?  There was a bug that was
supposedly fixed in 5.5.15 that I was experiencing, and I still see this
bug when I use this 5.5.0.0 which leads me to conclude I did not
really build 5.5.15.

Note: I can't use the binary 5.5.15 package because I have a requirement
to patch JNDIRealm.java, that's why I am starting from the source code.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: problem building 5.5.15

2006-02-13 Thread Eric Lenio
OK thanks for the tip.  Is there a document that goes into detail
on this?

On Mon, Feb 13, 2006 at 07:35:42PM +, Mark Thomas wrote:
> Eric Lenio wrote:
> > All -
> > 
> > Apologies in advance if this should go to tomcat-users but I'm
> > suspecting a problem with the way the source code is being distributed
> > so I'm starting here.
> > 
> > I downloaded the source file for 5.5.15 and built it.  After installing
> > it I ran bin/version.sh which said I had version 5.5.0.0.  Not what I
> > was expecting.
> This is the default version number set in build.properties.default
> 
> The behaviour you see is expected and can be changed by setting the
> appropriate ant properties.
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: problem building 5.5.15

2006-02-13 Thread Eric Lenio
Hi Mark, I would be happy to send in patches to the docs on how to build
Tomcat but I still need more info.  Let me rephrase my initial question.

Does there exist a module in the current subversion 
repository that has predefined all the properties to
generate a file that is the same as a release?

For example, I am attempting to generate apache-tomcat-5.5.15.tar.gz.
The current docs basically say "run ant".  Based on your earlier email I
know now that I'm supposed to first set the tomcat version properties.
OK so after ant finishes up, then what?  I think the next step is to
go into the build subdir and do 'ant release' but that's guesswork on my
part.  I'm looking to replicate the way you guys produce official 
releases.


On Mon, Feb 13, 2006 at 07:59:58PM +0000, Mark Thomas wrote:
> Eric Lenio wrote:
> > OK thanks for the tip.  Is there a document that goes into detail
> > on this?
> BUILDING.TXT and http://tomcat.apache.org/tomcat-5.5-doc/building.html
> are the main documents. Documentation patches are always welcome.
> 
> Mark
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: problem building 5.5.15

2006-02-15 Thread Eric Lenio
Well if the RM must generate this file for each release
perhaps then it could be added to subversion?

That way any time 'svn update' is used to refresh sources
the current Tomcat version can be known.

On Tue, Feb 14, 2006 at 08:28:04AM +0100, Mladen Turk wrote:
> 
> You will need to edit the build/build.properties.default
> and adjust the version numbers to preferred version.
> 
> It's up to RM to adjust them before releasing or building.
> We don't have actual version number inside the SVN, although
> we might add some sort of
> 
> 
> in the build.xml that would contain only version flags:
> 
> # - Vesion Control Flags -
> version.major=5
> version.minor=5
> version.build=1
> version.patch=16
> #Set the pretty version name
> version=5.5.16-dev
> 
> 
> Since that still implies that RM will still have to
> edit that file before releasing, you might as well create
> a build.properties file with the upper content.
> 
> The easiest thing would be to have a separate version
> property file updated regularly upon releases.
> 
> Regards,
> Mladen.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]