2010/1/14 Rainer Jung <rainer.j...@kippdata.de>: > Konstantin gave some arguments, why the use of @VERSION@ and similar ant > tags in top level text files (and filtering them) instead of directly using > explicit version numbers like 7 or 7.0 might not be good. The files are > - RELEASE-NOTES > - RUNNING.txt > - BUILDING.txt > and his arguments were > 1) I see no point. These are specific for the major.minor branch. > Turning them into a template looks wrong. > I do not expect doing merges to these files. > 2) It results in an unfiltered BUILDING.txt in our src bundles. > That is not pretty. This also affects our TC 7 builds. > If we agree on this I will replace the tags in trunk by the explicit version > numbers in those three files. The topic showed up, since I now backported > using the version tags from trunk to TC6 (except for those text files). > > I guess we can easily come to a uniform handling in TC6 and 7, either use > tags in those files as well, or explicit version numbers. I don't have a > strong opinion, so I'm fine with Konstantin's arguments. > > Any preferences? >
To expand my own comment, I think, that implementing filtering for these files just adds processing time required for our builds and a new feature to test/verify. These files are documentation, so if any changes are needed they can easily be done C-T-R, and I do not expect much changes / maintenance for these files. Content of the files is mostly version-specific. E.g. TC 6 requires JRE 5, but TC 7 JRE 6, TC 6 implements Servlets 2.5, TC 7 Servlets 3.0, etc. > * Download a source package from: > http://tomcat.apache.org/download-60.cgi By the way, the above was not replaced. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
