Re: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
[EMAIL PROTECTED] wrote: mturk 2004/02/13 06:14:14 Modified:procrun/bin tomcat.exe tomcatw.exe Log: Latest binaries. Thanks a lot :) So I'll wait a bit, see if Mark comments on bug 26906 (I think it's invalid: the fix seems to imply the URL sent by the client is always invalid), and then I'll put the 5.0.19 tag (and then someone will report a really Nasty Bug (TM), so I'll fix it and put in another 5.0.20 tag ;) ). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Remy Maucherat wrote: [EMAIL PROTECTED] wrote: mturk 2004/02/13 06:14:14 Modified:procrun/bin tomcat.exe tomcatw.exe Log: Latest binaries. Thanks a lot :) So I'll wait a bit, see if Mark comments on bug 26906 (I think it's invalid: the fix seems to imply the URL sent by the client is always invalid), and then I'll put the 5.0.19 tag (and then someone will report a really Nasty Bug (TM), so I'll fix it and put in another 5.0.20 tag ;) ). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I will tag jakarta-commons/daemon later this week-end and build the executables. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
I'll look at this now... Mark From: Remy Maucherat [mailto:[EMAIL PROTECTED] So I'll wait a bit, see if Mark comments on bug 26906 (I think it's invalid: the fix seems to imply the URL sent by the client is always invalid), and then I'll put the 5.0.19 tag (and then someone will report a really Nasty Bug (TM), so I'll fix it and put in another 5.0.20 tag ;) ). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Fixed. (with an alternative patch) From: Mark Thomas [mailto:[EMAIL PROTECTED] I'll look at this now... Mark From: Remy Maucherat [mailto:[EMAIL PROTECTED] So I'll wait a bit, see if Mark comments on bug 26906 (I think it's invalid: the fix seems to imply the URL sent by the client is always invalid), and then I'll put the 5.0.19 tag (and then someone will report a really Nasty Bug (TM), so I'll fix it and put in another 5.0.20 tag ;) ). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Mark Thomas wrote: Fixed. (with an alternative patch) Yes, the original patch really made it sound like the bug was invalid. Thanks. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
[EMAIL PROTECTED] wrote: billbarker2004/01/13 20:49:34 Modified:procrun/bin tomcat.exe tomcatw.exe Log: Updating versions of the Windows service executables. This is my first time with the new Tomcat build, so it can't hurt to test :). Also, if Mladen wants to over-write this, I've got no objection. Outstanding !! I'll test them of course :) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Remy Maucherat wrote: Ignacio J. Ortega wrote: Hola a todos: (Many time from my last post, things are settling here, so hope i will contribute some code in future :) shields up, nacho will be messing things shortly, now i'm only moderating our lists, and as some person said time ago moderation is to coding what washing dishes is to cooking :)) I know this was discussed before, but i dont really understand why it's needed to have a binary (moreover a win32 binary ) in CVS, and if there isn't a very good reason to do so, i'm against, and if there is a very good reason, i hope i should be applicable to any other binary we produce.. thing that i sincerely doubt .. Sorry to disagree, but it's impossible to build the said binaries without expensive compilers. (please do not suggest Cygwin) Why? Is the Makefile broken? So -1 to remove them, I need them where they are. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
- Original Message - From: jean-frederic clere [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Friday, October 10, 2003 12:52 AM Subject: Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe Remy Maucherat wrote: Ignacio J. Ortega wrote: Hola a todos: (Many time from my last post, things are settling here, so hope i will contribute some code in future :) shields up, nacho will be messing things shortly, now i'm only moderating our lists, and as some person said time ago moderation is to coding what washing dishes is to cooking :)) I know this was discussed before, but i dont really understand why it's needed to have a binary (moreover a win32 binary ) in CVS, and if there isn't a very good reason to do so, i'm against, and if there is a very good reason, i hope i should be applicable to any other binary we produce.. thing that i sincerely doubt .. Sorry to disagree, but it's impossible to build the said binaries without expensive compilers. (please do not suggest Cygwin) Why? Is the Makefile broken? AFAIK, no. It's just that Remy can't publish a version that requires Cygwin. And, as Remy has pointed out, to build a version of procrun that runs under a plain-vanilla install of Windows requires that you have a commercial (read MSVC) compiler. The cost of requiring this is just too high to demand of an O/S project. Now, if someone wants to suggest an O/S C-compiler for Windows that doesn't require Cygwin, I'm all ears :). So -1 to remove them, I need them where they are. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
-Original Message- From: jean-frederic clere Remy Maucherat wrote: Ignacio J. Ortega wrote: Sorry to disagree, but it's impossible to build the said binaries without expensive compilers. (please do not suggest Cygwin) Why? Is the Makefile broken? Doesn't matter. We need the tomcat.exe and tomcatw.exe only. While the tomcat.exe could be compiled using cygwin or mingw, there is a problem with tomcatw.exe. The GNU's resource compilers doesn't handle the BITMAP resources so we are missing those whenever building with those tools. Also I'm not sure about the License and Cygwin binaries (that's too fuzzy, so I don't even bother to compile something with cygwin). AFAICT we don't build WIN32 distributable binaries with those tools for any j-t-c project. Further more, apache2.x installation is build with InstallShield (another expensive tool), and nobody complains about that. So, find the space that can be reached from ant when building Tomcat5, and I'll put the binaries there, since we don't need them for anything but the nsis TC5 install package. So -1 to remove them, I need them where they are. As I said, you need them where they can be found duiring build process. MT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Bill Barker wrote: - Original Message - From: jean-frederic clere [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Friday, October 10, 2003 12:52 AM Subject: Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe Remy Maucherat wrote: Ignacio J. Ortega wrote: Hola a todos: (Many time from my last post, things are settling here, so hope i will contribute some code in future :) shields up, nacho will be messing things shortly, now i'm only moderating our lists, and as some person said time ago moderation is to coding what washing dishes is to cooking :)) I know this was discussed before, but i dont really understand why it's needed to have a binary (moreover a win32 binary ) in CVS, and if there isn't a very good reason to do so, i'm against, and if there is a very good reason, i hope i should be applicable to any other binary we produce.. thing that i sincerely doubt .. Sorry to disagree, but it's impossible to build the said binaries without expensive compilers. (please do not suggest Cygwin) Why? Is the Makefile broken? AFAIK, no. It's just that Remy can't publish a version that requires Cygwin. It does not require cygwin. And, as Remy has pointed out, to build a version of procrun that runs under a plain-vanilla install of Windows requires that you have a commercial (read MSVC) compiler. The cost of requiring this is just too high to demand of an O/S project. Now, if someone wants to suggest an O/S C-compiler for Windows that doesn't require Cygwin, I'm all ears :). So -1 to remove them, I need them where they are. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Mladen Turk wrote: -Original Message- From: jean-frederic clere Remy Maucherat wrote: Ignacio J. Ortega wrote: Sorry to disagree, but it's impossible to build the said binaries without expensive compilers. (please do not suggest Cygwin) Why? Is the Makefile broken? Doesn't matter. We need the tomcat.exe and tomcatw.exe only. While the tomcat.exe could be compiled using cygwin or mingw, there is a problem with tomcatw.exe. The GNU's resource compilers doesn't handle the BITMAP resources so we are missing those whenever building with those tools. Ok, I have noted the resources were missing but I have not tried to arrange it. Also I'm not sure about the License and Cygwin binaries (that's too fuzzy, so I don't even bother to compile something with cygwin). I will try to ask them. AFAICT we don't build WIN32 distributable binaries with those tools for any j-t-c project. Further more, apache2.x installation is build with InstallShield (another expensive tool), and nobody complains about that. :-(( So, find the space that can be reached from ant when building Tomcat5, and I'll put the binaries there, since we don't need them for anything but the nsis TC5 install package. I do not want to remove the binaries now, I am just reaching a Open Source way to produce them. So -1 to remove them, I need them where they are. As I said, you need them where they can be found duiring build process. MT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Mladen Turk a écrit : -Original Message- From: jean-frederic clere Remy Maucherat wrote: Ignacio J. Ortega wrote: Sorry to disagree, but it's impossible to build the said binaries without expensive compilers. (please do not suggest Cygwin) Why? Is the Makefile broken? Doesn't matter. We need the tomcat.exe and tomcatw.exe only. While the tomcat.exe could be compiled using cygwin or mingw, there is a problem with tomcatw.exe. The GNU's resource compilers doesn't handle the BITMAP resources so we are missing those whenever building with those tools. Also I'm not sure about the License and Cygwin binaries (that's too fuzzy, so I don't even bother to compile something with cygwin). AFAICT we don't build WIN32 distributable binaries with those tools for any j-t-c project. Further more, apache2.x installation is build with InstallShield (another expensive tool), and nobody complains about that. ASF (or just Apache Team) have a special aggrement with InstallShield so they could use it. May be we should ask the same to Microsoft for it's Visual C++ ;--) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Mladen Escribio: So, find the space that can be reached from ant when building Tomcat5, and I'll put the binaries there, since we don't need them for anything but the nsis TC5 install package. Ok, it seems reasonable, why dont release it as nigthlie, and put it where the nigthlies are just now ( i'm very out of sight on this, where are the nigthlies for any project just now, gumped? ), when a release comes ( is a release of procrun planned?) where the releases lie as ever.. not in cvs.. Saludos, Ignacio J. Ortega - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Hola a todos: (Many time from my last post, things are settling here, so hope i will contribute some code in future :) shields up, nacho will be messing things shortly, now i'm only moderating our lists, and as some person said time ago moderation is to coding what washing dishes is to cooking :)) I know this was discussed before, but i dont really understand why it's needed to have a binary (moreover a win32 binary ) in CVS, and if there isn't a very good reason to do so, i'm against, and if there is a very good reason, i hope i should be applicable to any other binary we produce.. thing that i sincerely doubt .. Saludos, Ignacio J. Ortega -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 9:20 AM To: [EMAIL PROTECTED] Subject: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe mturk 2003/10/09 00:19:55 Modified:procrun/bin tomcat.exe tomcatw.exe Log: Latest binaries (built with VC6/SP5) Revision ChangesPath 1.4 +28 -28 jakarta-tomcat-connectors/procrun/bin/tomcat.exe Binary file 1.4 +42 -39 jakarta-tomcat-connectors/procrun/bin/tomcatw.exe Binary file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Ignacio J. Ortega a écrit : Hola a todos: (Many time from my last post, things are settling here, so hope i will contribute some code in future :) shields up, nacho will be messing things shortly, now i'm only moderating our lists, and as some person said time ago moderation is to coding what washing dishes is to cooking :)) I know this was discussed before, but i dont really understand why it's needed to have a binary (moreover a win32 binary ) in CVS, and if there isn't a very good reason to do so, i'm against, and if there is a very good reason, i hope i should be applicable to any other binary we produce.. thing that i sincerely doubt .. I agree with nacho, exec bins should be only be present in tarball/zip, not in CVS. CVS is a source repository ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
Ignacio J. Ortega wrote: Hola a todos: (Many time from my last post, things are settling here, so hope i will contribute some code in future :) shields up, nacho will be messing things shortly, now i'm only moderating our lists, and as some person said time ago moderation is to coding what washing dishes is to cooking :)) I know this was discussed before, but i dont really understand why it's needed to have a binary (moreover a win32 binary ) in CVS, and if there isn't a very good reason to do so, i'm against, and if there is a very good reason, i hope i should be applicable to any other binary we produce.. thing that i sincerely doubt .. Sorry to disagree, but it's impossible to build the said binaries without expensive compilers. (please do not suggest Cygwin) So -1 to remove them, I need them where they are. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Committing binaries in CVS [Was] RE: cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 12:34 PM Sorry to disagree, but it's impossible to build the said binaries without expensive compilers. (please do not suggest Cygwin) Disagreeing is the salt of email lists, so not worries about disagreeing :) Do you need them to build installable packages, at least i understand now, what about to release them? you could use them from release, same thing that right now is done with any other binary needed, moreover we were depending on nigthlies from commons and other things, i dont know why we should not do the same in this case.. Saludos, Ignacio J. Ortega - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
