On 24/08/2015 16:40, Alten, Jessica-Aileen wrote: >> The official position of the ASF is that we provide code, not >> binaries. > > Sorry, I can't follow this argument - there are lots of binaries in the > download area, even for Tomcat and the Httpd flagship.
ASF policy is that we MUST release in source code form. Many projects provide convenience binaries but they are just that, convenience binaries. >> We'd love to provide Windows binaries for mod_jk, but they are a real >> pain in the neck to actually build: they require very specific build >> environment, and the library must be built in such a way that it's >> compatible with the web server in which it's running (e.g. httpd >> 1.3/2.2/2.4 or IIS 5/6/7/8/9, proper architecture (32/63) and chipset >> (x86/x86-64/itanium/alpha). It's gotten to the point where it's tough >> to provide all of those combinations with any regularity. > > I understand that it is difficult - perhaps too difficult for the developers > of this module, but the average Windows admin or Java programmer should do > this? ;) > There were binaries of this module at least for the last 10 years! > I'm very disappointed on this attitude. You are closing out the whole > Windows/IIS world. Yes, we (the Tomcat community) has a problem here. We needed a jk release to address a security issue that had been made public before we were ready. The developers that normally work on jk have been quiet lately so one of the other Tomcat developers stepped up to do the release. The source code side of things is relatively simple but the binaries are not and the document build process is not sufficient to generate a binary release. To give you an idea, this is the documented build process for the tc-native DLL: http://tomcat.apache.org/native-doc/#Building/Windows This is what is actually required to generate a release: http://wiki.apache.org/tomcat/BuildTcNativeWin This is the documented build process for ISAPI: http://svn.apache.org/viewvc/tomcat/jk/trunk/native/iis/README?view=annotate We don't have the equivalent 'How to build a release' documentation. It is not at all clear how release builds (which options have been used, what have they been compiled with / against?) have been built in the past so it is next to impossible to reproduce a similar build. >> Unfortunately, I don't believe they provide builds for the ISAPI >> redirector for IIS. If that's what you need... umm... > > Umm - yes - this is what I need. There are a couple of options: Hope the jk committers provide enough information to document the release process so anyone can run it. Figure out how to build something that works for you and share that with the Tomcat community so anyone can build it. Then one of the active Tomcat committers will be able to include the binary in the next release (and provide an official binary for this release). Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
