It looks like you've got an embedded Tomcat5 server/container that Cargo is deploying to... is that correct? If so, you probably need to change that and deploy to a stand-alone, normally installed Tomcat5. Then I think Cargo should deploy and exit after the deployment is successful or fails.
Realistically, this question should be sent to the Cargo Users list as they may have better/more advice than we can offer. Wayne On 4/20/07, Bart Warnez <[EMAIL PROTECTED]> wrote:
Hello, I made a plan to deploy our builds into Tomcat 5 with the maven plugin "cargo". I scheduled it as daily builds. The problem is that the build never stops. The last lines of the activity log look like this: 20-avr.-2007 14:32:48 INFO talledLocalContainer INFO: Server startup in 42594 ms 20-avr.-2007 14:32:50 INFO talledLocalContainer Tomcat 5.5.23 started on port 8080 20-avr.-2007 14:32:50 INFO Press Ctrl-C to stop the container... If the next day, when the plan is scheduled to run again, the previous build is automatically stopped and the new one starts, I wouldn't really make a problem of this, becoz at least, the build is refreshed every day and I can always see the newest webapp on my browser. But, the old running build blocks the new build, so I would have to manually stop the old build and restart the plan. Is there any solution to this? Grtz, Bart -- View this message in context: http://www.nabble.com/Bamboo-and-cargo%3A-endless-builds-tf3617872s177.html#a10101963 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
