Chris, I submitted the bug, with the patch. Got an initial response that the class will not be included in 7.x, but no answer yet on whether it will be fixed. Thanks again for the direction.
-----Original Message----- From: Electronjockey [mailto:electronjoc...@hotmail.com] Sent: Monday, March 15, 2010 1:32 PM To: Tomcat Users List Subject: Re: org.apache.jk.config.ApacheConfig modJk Chris, Yeah, the xampp site has some wackiness to it. I got it from the link here: http://www.apachefriends.org/en/xampp-windows.html#644 or from here: http://sourceforge.net/projects/xampp/files/ and thanks for the info on the svn procs. I'm workin' it and will submit the bug with the diff shortly. -----Original Message----- From: Christopher Schultz <ch...@christopherschultz.net> To : Tomcat Users List <users@tomcat.apache.org> Sent: Mon Mar 15 13:23:12 2010 Subject: Re: org.apache.jk.config.ApacheConfig modJk -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Todd, On 3/15/2010 12:57 PM, Electronjockey wrote: The official add-on is Tomcat 6.0.20 and mod_jk 1.2.20. Hmm... I must have been looking in the wrong place. I went from here: http://www.apachefriends.org/en/faq-xampp-windows.html to here http://www.apachefriends.org/en/faq-xampp-windows.html#addons to here http://sourceforge.net/projects/xamppaddon/ ...and that project had an update over a year ago for Tomcat 5.0.27. Is there a better place to find information about XAMPP plug-ins? I'm proceeding with a static mod_jk.conf for the time being. And yes, I totally agree with you on the bug vs. inconvenience assessment. The issue struck me as more of a QA issue than anything. How would I submit the fix? Is there a document outlining the procedure on the tomcat/apache site? The change is to line 138 of the source. You might want to read this before you start: http://tomcat.apache.org/bugreport.html Then, file a bug in bugzilla: https://issues.apache.org/bugzilla/ Remember to file the bug against the correct product and version. Once you've filed your bug, attach a patch to the bug. If your patch is really small and/or you don't know how to use UNIX diff, you can just explain in the bug description or a comment what needs to be changed. I'm still trying to get my project setup for a custom build, but I'm seriously multitasking right now, and I'm not at all experienced with SVN access. All youll have to do is create a patch file. With svn it's easy: make your changes, then do: $ svn diff [files] > my.patch Then, upload that file. You might want to check the patch to make sure it's not including something that's not really part of the patch, such as oddball changes you made to the makefiles or whatever :) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuebQAACgkQ9CaO5/Lv0PDQqgCdHxFm48ZYSmWSBLNihZ+cXhaq FPYAoKGFsRwpgi3Iuh1VKve0BUXRyt7U =IHZG -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
