RE: How to remove a hanging build process
I have the same thing happening. The best I can tell you is to click on build all and then kill all processes. That should return the system to a state you can build from, however you will never get rid of the failed build and it will continue to show it as running for the rest of this versions life. You simply have to ignore it and move on. I was told that this bug should be fixed in the next release which we are eagerly awaiting. Tony -Original Message- From: Anoop kumar V [mailto:[EMAIL PROTECTED] Sent: Saturday, January 13, 2007 11:15 PM To: continuum-users@maven.apache.org Subject: Re: How to remove a hanging build process By build task you mean the java task that shows up in a ps -ef? Cant you just kill the task using the kill pid command? Anoop On 1/13/07, Andreas Guther [EMAIL PROTECTED] wrote: Hi, We are using Continuum 1.0.3. I have a build task that is hanging somehow now for several days. The delete icon is disabled and I cannot find a way to either kill or remove the task from the builds. Is there a way to get rid of this task? Andreas -- Thanks and best regards, Anoop
JAVA_HOME
I need some help in setting the JAVA_HOME environment variable to run when the server is restarted? I use JAVA_HOME for several programs and I can not figure out how to set this for continuum. I can get this set in every app except apache/maven continuum. I have tried the following in the startup script in /etc/init.d/continuum and both will work if I log in and restart continuum manually, but do not work if the server is restarted and I do not log in. 1) I added the following lines at the beginning of the init script JAVA_HOME=/usr/java/j2re1.4.2_03 Export JAVA_HOME And 2) created a file with the following content JAVA_HOME=/usr/java/j2re1.4.2_03 Export JAVA_HOME I then sourced this file at the beginning of the init script . test.txt I have both the variable and export lines in my profile, so when I log into the server and start continuum it starts up and I can run a build, because JAVA_HOME is set by the profile. If I log out continuum continues to operate and I am still able to complete a build, apparently because the app has already determined when JAVA_HOME is. If I remark out the variable and export lines from my profile, continuum will run, but I can not get a build to complete. I get these same results if I do not log in. With the lines remarked out in my profile I can add the JAVA_HOME to the path and get a build to complete, but the PATH gets unset when I log out. Any help would be great Tony
stop a build
How do you stop a build in progress? I have tried restarting continuum, restarting the server, killing all java procs and nothing seems to work. Tony
RE: debian start up
Good call! No it was not. The strange part of this issue was that JAVA_HOME was set in the default user profile, so when you logged onto the system JAVA_HOME got set and everything worked fine. I added this to the init script /etc/init.d/continuum and that fixed it. JAVA_HOME=/usr/java/j2re1.4.2_03 export JAVA_HOME Thanks Tony -Original Message- From: David J. M. Karlsen [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 6:58 AM To: continuum-users@maven.apache.org Subject: Re: debian start up Tony Heal wrote: I am having problems getting continuum (v1.0.3) to start on a debian (sarge v3.1) system. If the server is restarted continuum tries to start up, but receives a shutdown signal from something I can not find. After I log back in I can start up continuum without any problems at all. Has anyone had any issues with the server start process? Is JAVA_HOME available as a variable when the script tries to start continuum? -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com
debian start up
I am having problems getting continuum (v1.0.3) to start on a debian (sarge v3.1) system. If the server is restarted continuum tries to start up, but receives a shutdown signal from something I can not find. After I log back in I can start up continuum without any problems at all. Has anyone had any issues with the server start process? Tony
