I see up to 7.0.32 on the
stable svn branch:
Apache Tomcat - Subversion Repository Access
but 7.0.30 is proffered on the main page:
Apache Tomcat - Welcome!
I would go with 7.0.32 just because if you have a bug, the world is full of people who say "try the latest release and see if you can duplicate it." I would use JAVA 1.7__latest, too, for similar reasons and to push obsolescence that much farther out. Once you get it running and in production, then it takes a lot of hopefully automated regression testing to verify a new release of either is viable. By that time, neither will be the latest. If you have the regression tests, and keep their coverage up with discovered problems, you can keep your prod up to date. Update you-wrote-it code that adjusts functionality in separate releases from new revisions of bought/downloaded stuff, so you never blame the wrong shop and it saves time. Of course, sometime you need to change the first to accomodate the second, but the changes should be backward compatible to the old tomcat/jdk.