On 17/09/2010 13:56, André Warnier wrote: > Mark Thomas wrote: >> If you do get involved then the process would be something along the >> lines of: >> (one time tasks) >> - install svn >> - install ant >> - checkout source >> - build Tomcat >> (per change task) > > Sorry if I ask, but I am really unfamiliar with these things. > Does this involve any actual compiling of code ?
It is actually easier to do a full build of both the code and the docs since that is how the build is configured by default. You then also get a ready to run Tomcat instance with the updated docs deployed. > I mean, if the only thing that is changed is some documentation page, it > won't I guess. The build is reasonably incremental. A doc change shouldn't trigger a rebuild of any code. However, since you would be working with trunk, you'd need to do an "svn up" to ensure you had the latest versions. That might change code which would trigger a rebuild of that class. > But would the build break just because there is no > compiler available ? It is going to get complicated if you don't have a JDK to hand. > I guess I've just lost all my guru points here. Not at all. A key feature of being a guru is knowing what you *don't* know. If you want to start down this path and see how it goes, I am happy to talk you through step by step. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
