2010/1/4 Rainer Jung <rainer.j...@kippdata.de>: > On 04.01.2010 15:53, Mladen Turk wrote: >> >> On 01/04/2010 02:10 PM, Henri Gomez wrote: >>> >>> It's not the case in the OS/X version >>> >> >> Nope. the windows .rc file wasn't updated >> before 1.1.18 tag, so when you compile a .dll >> and check it's resource version, it reports 1.1.16 >> >> This can be a problem with some third party install >> tools that depend on version number in .dll for >> updating the file (might be even our nsis does the >> same thing, so the .dll won't get overwritten if >> installed over the exiting version). > > That's what Mladen means: > > http://svn.apache.org/viewvc?rev=893131&view=rev > > The version numbers are usually updated after a release is done, the > TCN_IS_DEV_VERSION toggle is flipped before the release to "0" and after the > release back to "1". > > Mladen fixed the rc file in the tag after tagging, so you won't find the bug > in the tag any more. > > Regards, > > Rainer >
The compiled "tcnative-.dll" DLLs on http://www.apache.org/dist/tomcat/tomcat-connectors/native/1.1.18/binaries/win(32|64) all show "1.1.18.0" on the Version tab in the File Properties dialog in Windows Explorer. The same with the ones in 6.0.22 RC binary bundles (the same files). Am I missing something? Do we really have a problem? > Should we update the recommended version in AprLifecycleListener to 19? > At the moment we have recommended=17 and required=17. My understanding is that all .17 .. .19 are compatible. So the answer is "No". We should update "build.properties.default" files to pull the up-to-date bundles when building. BTW, TC 7 and TC 5.5 still reference 1.1.16 in their build.properties. Maybe that caused the confusion? Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
