RE: Procrun improvements
Howdy, OK, I just nominated you on commons-dev ;) (So that's a thread you might want to watch) ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Tuesday, December 30, 2003 12:20 AM To: [EMAIL PROTECTED] Subject: Re: Procrun improvements Well, I admit that I don't follow commons-dev as closely as other lists, but a quick search of Eyebrowse doesn't turn up any such item :). And I am most definitely karmically-challenged wrt Commons ;-). Shapira, Yoav [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Howdy, I think the following two items should be supported: - I think it should be possible to specify a path to the JVM base directory (this feature is supposed to be present, but doesn't actually work for reasons I can't remember); using the config dialog to change the JVM path makes the config dialog refuse to start again - when using java, procrun should look at the JAVA_HOME env property before looking in the registry, to be consistent with all Java based tools available If you want to open a commons BZ item for this, I can attach patches for it (I'm not a commons committer, so the round-about is all we've got if you want to go through me :). Definitely the JAVA_HOME environment is more important for me (I'm a unix person ;)). Bill, I thought we took care of making you a commons committer already? I'm 99% sure I voted +1 on that?? Anyways, if not, I'll nominate you, and I can commit commons patches (and be a release manager) until then. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Procrun improvements
Mladen Turk a écrit : -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] The question is do you need the mentioned features _now_, if there is a new release on the horizon, or this can wait for a week or two? It would be good to have a new tag for TC 5 relativelely shortly ( 2 weeks) :) I think adding support for JAVA_HOME could be good enough for this release. OK then. Think that Bill send a patch a while ago (I'll browse my archive). Did some of you take a look at the Eclipse project which use a nice Java Starter App ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Procrun improvements
Howdy, I think the following two items should be supported: - I think it should be possible to specify a path to the JVM base directory (this feature is supposed to be present, but doesn't actually work for reasons I can't remember); using the config dialog to change the JVM path makes the config dialog refuse to start again - when using java, procrun should look at the JAVA_HOME env property before looking in the registry, to be consistent with all Java based tools available If you want to open a commons BZ item for this, I can attach patches for it (I'm not a commons committer, so the round-about is all we've got if you want to go through me :). Definitely the JAVA_HOME environment is more important for me (I'm a unix person ;)). Bill, I thought we took care of making you a commons committer already? I'm 99% sure I voted +1 on that?? Anyways, if not, I'll nominate you, and I can commit commons patches (and be a release manager) until then. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Procrun improvements
Well, I admit that I don't follow commons-dev as closely as other lists, but a quick search of Eyebrowse doesn't turn up any such item :). And I am most definitely karmically-challenged wrt Commons ;-). Shapira, Yoav [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Howdy, I think the following two items should be supported: - I think it should be possible to specify a path to the JVM base directory (this feature is supposed to be present, but doesn't actually work for reasons I can't remember); using the config dialog to change the JVM path makes the config dialog refuse to start again - when using java, procrun should look at the JAVA_HOME env property before looking in the registry, to be consistent with all Java based tools available If you want to open a commons BZ item for this, I can attach patches for it (I'm not a commons committer, so the round-about is all we've got if you want to go through me :). Definitely the JAVA_HOME environment is more important for me (I'm a unix person ;)). Bill, I thought we took care of making you a commons committer already? I'm 99% sure I voted +1 on that?? Anyways, if not, I'll nominate you, and I can commit commons patches (and be a release manager) until then. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Procrun improvements
Mladen Turk wrote: There are some problems with procrun for the VM setup. Right now, the only setting which works AFAIK is using java and letting procrun detect the VM using the Windows registry. The procrun is a little bit clumsy to maintain. I'm working on the 2.0 version that will have spitted code in few files that will be easier to maintain, with lots of enhancements. The question is do you need the mentioned features _now_, if there is a new release on the horizon, or this can wait for a week or two? It would be good to have a new tag for TC 5 relativelely shortly ( 2 weeks) :) I think adding support for JAVA_HOME could be good enough for this release. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Procrun improvements
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Sunday, December 28, 2003 1:42 AM Subject: Procrun improvements Hi, There are some problems with procrun for the VM setup. Right now, the only setting which works AFAIK is using java and letting procrun detect the VM using the Windows registry. I think the following two items should be supported: - I think it should be possible to specify a path to the JVM base directory (this feature is supposed to be present, but doesn't actually work for reasons I can't remember); using the config dialog to change the JVM path makes the config dialog refuse to start again - when using java, procrun should look at the JAVA_HOME env property before looking in the registry, to be consistent with all Java based tools available If you want to open a commons BZ item for this, I can attach patches for it (I'm not a commons committer, so the round-about is all we've got if you want to go through me :). Rémy - 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: Procrun improvements
-Original Message- From: Remy Maucherat Subject: Procrun improvements Hi, There are some problems with procrun for the VM setup. Right now, the only setting which works AFAIK is using java and letting procrun detect the VM using the Windows registry. The procrun is a little bit clumsy to maintain. I'm working on the 2.0 version that will have spitted code in few files that will be easier to maintain, with lots of enhancements. The question is do you need the mentioned features _now_, if there is a new release on the horizon, or this can wait for a week or two? MT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Procrun improvements
-Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] The question is do you need the mentioned features _now_, if there is a new release on the horizon, or this can wait for a week or two? It would be good to have a new tag for TC 5 relativelely shortly ( 2 weeks) :) I think adding support for JAVA_HOME could be good enough for this release. OK then. Think that Bill send a patch a while ago (I'll browse my archive). MT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Procrun improvements
- Original Message - From: Mladen Turk [EMAIL PROTECTED] To: 'Tomcat Developers List' [EMAIL PROTECTED] Sent: Sunday, December 28, 2003 3:07 AM Subject: RE: Procrun improvements -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] The question is do you need the mentioned features _now_, if there is a new release on the horizon, or this can wait for a week or two? It would be good to have a new tag for TC 5 relativelely shortly ( 2 weeks) :) I think adding support for JAVA_HOME could be good enough for this release. OK then. Think that Bill send a patch a while ago (I'll browse my archive). I'd been meaning to, but didn't get around it. They are attached to BZ #25789. I was going to use the jsvc code that parses 'jvm.cfg', except that Sun changed the format in 1.4, and deprecated the file (:. MT. - 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]
