[EMAIL PROTECTED] wrote: > On Thu, 29 Aug 2002, jean-frederic clere wrote: > > >>I am +1 for merging the code but in daemon. I am using the daemon code for >>projects not related with mod_jk and I would perfer to have it independant from >>mod_jk. >>An other point to be against moving it in mod_jk is that the code has been moved >>recently in commons (sandbox) I do not thing that it is a good idea to move it >>back in the Tomcat repos. >>Also if we move it from daemon to mod_jk we have to ask it to the common dev >>list before moving it. > > > Ok, not 'move'. What about 'copy' :-) ? > > There is a lot of duplication, I just want to make sure that jk has all > the features that it needs - starting the VM is one thing I want to review > and 'copy', if there's something that we missed in jk. I would also like > to 'copy' the service monitor and copy and modify the service > registration ( I like the jk_nt_service properties file, but the code is > a bit ugly right now ).
I still see no good reasons to make a 'copy'... Surely the code in daemon needs a cleaning and some changes to fit mod_jk needs. A "ant download" task could bring the needed source in the mod_jk directory to ease the release mechanism. I will try to find time to get the JVM started under Apache as it was in mod_jserv using the code in daemon. > > > Costin > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
