RE: Starting/Stopping Resin with Ant
Hi Matt, Feel free to send as many emails as you with to the cactus mailing list. We can help you! Also, if you feel the need to discuss things, my yahoo id is: vmassol Thanks -Vincent > -Original Message- > From: Matt Raible [mailto:[EMAIL PROTECTED] > Sent: 25 February 2004 16:47 > To: Cactus Users List > Subject: Re: Starting/Stopping Resin with Ant > > Comments at bottom... > > On Feb 25, 2004, at 6:02 AM, Vincent Massol wrote: > > > > > > >> -Original Message- > >> From: Christopher Lenz [mailto:[EMAIL PROTECTED] > >> Sent: 25 February 2004 13:26 > >> To: Cactus Users List > >> Subject: Re: Starting/Stopping Resin with Ant > >> > >> Am 25.02.2004 um 11:07 schrieb Vincent Massol: > >>>> -Original Message- > >>>> From: Christopher Lenz [mailto:[EMAIL PROTECTED] > >>>> Sent: 25 February 2004 10:56 > >>>> To: Cactus Users List > >>>> Subject: Re: Starting/Stopping Resin with Ant > >>>> > >>>> In that case I'd suggest extending so that it > > would > >>>> accept a nested , similar to . This approach > >>>> would be much cleaner than providing separate and > >>>> tasks IMHO. > >>> > >>> Except that : > >>> 1/ we don't need/want a containerset, just a single container > > (unless > >>> you wish to start several containers in parallel). > >> > >> is simply the data type, basically the main interface > >> through which you access the functionality provider by the container > >> package from an Ant build file. There is currently no such thing as a > >> container outside of a containerset, although we could probably > > provide > >> support for that for Ant 1.6 build files (while still working in 1.5). > >> > >> Second, multiple containers would not be run parallel, but > >> sequentially. The nested "test" task would be repeated for every > >> container. > > > > Ok I see. My initial idea was to provide 2 simple start/stop tasks and > > leave it for the user to do whatever he wishes before after it is > > started. But you're right, we also provide the hook to do something in > > between and support the stop after the start. > > > > I'm fine with your solution or modifying runservertests to support > > automatic start/stop. > > > >> > >>> 2/ it's not about run server tests. It's simply about starting a > >>> container. Thus the name is misleading. I'd much prefer a new task. > >> > >> The name was always misleading, as you can use for > >> everything you like. Still, it is mostly used for tests, because the > >> container is shut down after whatever you wanted to do is finished, > > and > >> that functionality is not very useful in non-test related contexts. > > I'm > >> not against changing the name, however. > > > > ok > > > >> > >>>> That can get messy though, because the task basically gets two > >>>> different modes: the first is using the classic start/stop hooks, > > the > >>>> second mode would be based on container sets. Note that the first > > mode > >>>> could be dropped, because a generic container inside a container > > set > >>>> supports the same semantics, but simply dropping the start/stop > > hooks > >>>> would break backward compatibility. I recall working on this, but > > gave > >>>> up because I didn't need it myself. > >>>> > >>>> This would be simpler if we'd simply make this a new task > >>>> ( or ?). > >>> > >>> that's what I'm proposing with > >>> startcontainer/stopcontainer/runcontainer > >>> I think. > >> > >> is okay. As I said before, I'm not in favor of separate > >> start/stop tasks because that is s procedural (yuck ;-) ). We want > >> a more declarative syntax, like: > >> > >> run tomcat4x so I can: > >>run all my integration unit tests > >>run all my functional tests based on canoo webtest or whatever > >> > >> So how about: > >> > >> > >> > >> > >> > >> > >> > >> > >> In Ant 1.6 we drop the : > >> > >> > >> > >> > >> > >> > >> > >> > >> Basically, we can also drop the block, but I think it is > >> nice in keeping the actual tasks together in a block. > >> > >> Does that sound okay? > > > > Yep. +1 from me. runservertests will be deprecated and replaced with > > runcontainer. > > > > Matt, what do you think? > > > > Thanks > > -Vincent > > I don't think I know enough about what I'm doing to comment on this. > Once I've dug in and understand how everything works, then I'll report > back with my findings and a proposed solution. We can then discuss how > my solution should be improved to fit the greater need. > > Matt > > > - > 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: Starting/Stopping Resin with Ant
Comments at bottom... On Feb 25, 2004, at 6:02 AM, Vincent Massol wrote: -Original Message- From: Christopher Lenz [mailto:[EMAIL PROTECTED] Sent: 25 February 2004 13:26 To: Cactus Users List Subject: Re: Starting/Stopping Resin with Ant Am 25.02.2004 um 11:07 schrieb Vincent Massol: -Original Message- From: Christopher Lenz [mailto:[EMAIL PROTECTED] Sent: 25 February 2004 10:56 To: Cactus Users List Subject: Re: Starting/Stopping Resin with Ant In that case I'd suggest extending so that it would accept a nested , similar to . This approach would be much cleaner than providing separate and tasks IMHO. Except that : 1/ we don't need/want a containerset, just a single container (unless you wish to start several containers in parallel). is simply the data type, basically the main interface through which you access the functionality provider by the container package from an Ant build file. There is currently no such thing as a container outside of a containerset, although we could probably provide support for that for Ant 1.6 build files (while still working in 1.5). Second, multiple containers would not be run parallel, but sequentially. The nested "test" task would be repeated for every container. Ok I see. My initial idea was to provide 2 simple start/stop tasks and leave it for the user to do whatever he wishes before after it is started. But you're right, we also provide the hook to do something in between and support the stop after the start. I'm fine with your solution or modifying runservertests to support automatic start/stop. 2/ it's not about run server tests. It's simply about starting a container. Thus the name is misleading. I'd much prefer a new task. The name was always misleading, as you can use for everything you like. Still, it is mostly used for tests, because the container is shut down after whatever you wanted to do is finished, and that functionality is not very useful in non-test related contexts. I'm not against changing the name, however. ok That can get messy though, because the task basically gets two different modes: the first is using the classic start/stop hooks, the second mode would be based on container sets. Note that the first mode could be dropped, because a generic container inside a container set supports the same semantics, but simply dropping the start/stop hooks would break backward compatibility. I recall working on this, but gave up because I didn't need it myself. This would be simpler if we'd simply make this a new task ( or ?). that's what I'm proposing with startcontainer/stopcontainer/runcontainer I think. is okay. As I said before, I'm not in favor of separate start/stop tasks because that is s procedural (yuck ;-) ). We want a more declarative syntax, like: run tomcat4x so I can: run all my integration unit tests run all my functional tests based on canoo webtest or whatever So how about: In Ant 1.6 we drop the : Basically, we can also drop the block, but I think it is nice in keeping the actual tasks together in a block. Does that sound okay? Yep. +1 from me. runservertests will be deprecated and replaced with runcontainer. Matt, what do you think? Thanks -Vincent I don't think I know enough about what I'm doing to comment on this. Once I've dug in and understand how everything works, then I'll report back with my findings and a proposed solution. We can then discuss how my solution should be improved to fit the greater need. Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Starting/Stopping Resin with Ant
> -Original Message- > From: Christopher Lenz [mailto:[EMAIL PROTECTED] > Sent: 25 February 2004 13:26 > To: Cactus Users List > Subject: Re: Starting/Stopping Resin with Ant > > Am 25.02.2004 um 11:07 schrieb Vincent Massol: > >> -Original Message- > >> From: Christopher Lenz [mailto:[EMAIL PROTECTED] > >> Sent: 25 February 2004 10:56 > >> To: Cactus Users List > >> Subject: Re: Starting/Stopping Resin with Ant > >> > >> In that case I'd suggest extending so that it would > >> accept a nested , similar to . This approach > >> would be much cleaner than providing separate and > >> tasks IMHO. > > > > Except that : > > 1/ we don't need/want a containerset, just a single container (unless > > you wish to start several containers in parallel). > > is simply the data type, basically the main interface > through which you access the functionality provider by the container > package from an Ant build file. There is currently no such thing as a > container outside of a containerset, although we could probably provide > support for that for Ant 1.6 build files (while still working in 1.5). > > Second, multiple containers would not be run parallel, but > sequentially. The nested "test" task would be repeated for every > container. Ok I see. My initial idea was to provide 2 simple start/stop tasks and leave it for the user to do whatever he wishes before after it is started. But you're right, we also provide the hook to do something in between and support the stop after the start. I'm fine with your solution or modifying runservertests to support automatic start/stop. > > > 2/ it's not about run server tests. It's simply about starting a > > container. Thus the name is misleading. I'd much prefer a new task. > > The name was always misleading, as you can use for > everything you like. Still, it is mostly used for tests, because the > container is shut down after whatever you wanted to do is finished, and > that functionality is not very useful in non-test related contexts. I'm > not against changing the name, however. ok > > >> That can get messy though, because the task basically gets two > >> different modes: the first is using the classic start/stop hooks, the > >> second mode would be based on container sets. Note that the first mode > >> could be dropped, because a generic container inside a container set > >> supports the same semantics, but simply dropping the start/stop hooks > >> would break backward compatibility. I recall working on this, but gave > >> up because I didn't need it myself. > >> > >> This would be simpler if we'd simply make this a new task > >> ( or ?). > > > > that's what I'm proposing with > > startcontainer/stopcontainer/runcontainer > > I think. > > is okay. As I said before, I'm not in favor of separate > start/stop tasks because that is s procedural (yuck ;-) ). We want > a more declarative syntax, like: > > run tomcat4x so I can: >run all my integration unit tests >run all my functional tests based on canoo webtest or whatever > > So how about: > > > > > > > > > In Ant 1.6 we drop the : > > > > > > > > > Basically, we can also drop the block, but I think it is > nice in keeping the actual tasks together in a block. > > Does that sound okay? Yep. +1 from me. runservertests will be deprecated and replaced with runcontainer. Matt, what do you think? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Starting/Stopping Resin with Ant
Am 25.02.2004 um 11:07 schrieb Vincent Massol: -Original Message- From: Christopher Lenz [mailto:[EMAIL PROTECTED] Sent: 25 February 2004 10:56 To: Cactus Users List Subject: Re: Starting/Stopping Resin with Ant In that case I'd suggest extending so that it would accept a nested , similar to . This approach would be much cleaner than providing separate and tasks IMHO. Except that : 1/ we don't need/want a containerset, just a single container (unless you wish to start several containers in parallel). is simply the data type, basically the main interface through which you access the functionality provider by the container package from an Ant build file. There is currently no such thing as a container outside of a containerset, although we could probably provide support for that for Ant 1.6 build files (while still working in 1.5). Second, multiple containers would not be run parallel, but sequentially. The nested "test" task would be repeated for every container. 2/ it's not about run server tests. It's simply about starting a container. Thus the name is misleading. I'd much prefer a new task. The name was always misleading, as you can use for everything you like. Still, it is mostly used for tests, because the container is shut down after whatever you wanted to do is finished, and that functionality is not very useful in non-test related contexts. I'm not against changing the name, however. That can get messy though, because the task basically gets two different modes: the first is using the classic start/stop hooks, the second mode would be based on container sets. Note that the first mode could be dropped, because a generic container inside a container set supports the same semantics, but simply dropping the start/stop hooks would break backward compatibility. I recall working on this, but gave up because I didn't need it myself. This would be simpler if we'd simply make this a new task ( or ?). that's what I'm proposing with startcontainer/stopcontainer/runcontainer I think. is okay. As I said before, I'm not in favor of separate start/stop tasks because that is s procedural (yuck ;-) ). We want a more declarative syntax, like: run tomcat4x so I can: run all my integration unit tests run all my functional tests based on canoo webtest or whatever So how about: In Ant 1.6 we drop the : Basically, we can also drop the block, but I think it is nice in keeping the actual tasks together in a block. Does that sound okay? Chris -- Christopher Lenz /=/ cmlenz at gmx.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Starting/Stopping Resin with Ant
Hi Chris, > -Original Message- > From: Christopher Lenz [mailto:[EMAIL PROTECTED] > Sent: 25 February 2004 10:56 > To: Cactus Users List > Subject: Re: Starting/Stopping Resin with Ant > > Am 25.02.2004 um 10:15 schrieb Vincent Massol: > >> I believe we already have this functionality in > >> (although not documented): > >> > >> > >> > >> > >> > >>Here we go > >> > >> > >> > >> > >> > > > > But you'll have to implement the start.resin goal no? It's not calling > > the o.a.c.i.a.c.resin.* classes , right? > > Ah, I thought I was missing something :-) > > In that case I'd suggest extending so that it would > accept a nested , similar to . This approach > would be much cleaner than providing separate and > tasks IMHO. Except that : 1/ we don't need/want a containerset, just a single container (unless you wish to start several containers in parallel). 2/ it's not about run server tests. It's simply about starting a container. Thus the name is misleading. I'd much prefer a new task. > > That can get messy though, because the task basically gets two > different modes: the first is using the classic start/stop hooks, the > second mode would be based on container sets. Note that the first mode > could be dropped, because a generic container inside a container set > supports the same semantics, but simply dropping the start/stop hooks > would break backward compatibility. I recall working on this, but gave > up because I didn't need it myself. > > This would be simpler if we'd simply make this a new task > ( or ?). that's what I'm proposing with startcontainer/stopcontainer/runcontainer I think. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Starting/Stopping Resin with Ant
Am 25.02.2004 um 10:15 schrieb Vincent Massol: I believe we already have this functionality in (although not documented): Here we go But you'll have to implement the start.resin goal no? It's not calling the o.a.c.i.a.c.resin.* classes , right? Ah, I thought I was missing something :-) In that case I'd suggest extending so that it would accept a nested , similar to . This approach would be much cleaner than providing separate and tasks IMHO. That can get messy though, because the task basically gets two different modes: the first is using the classic start/stop hooks, the second mode would be based on container sets. Note that the first mode could be dropped, because a generic container inside a container set supports the same semantics, but simply dropping the start/stop hooks would break backward compatibility. I recall working on this, but gave up because I didn't need it myself. This would be simpler if we'd simply make this a new task ( or ?). Cheers, Chris -- Christopher Lenz /=/ cmlenz at gmx.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Starting/Stopping Resin with Ant
Hi Chris, > -Original Message- > From: Christopher Lenz [mailto:[EMAIL PROTECTED] > Sent: 25 February 2004 09:39 > To: Cactus Users List > Subject: Re: Starting/Stopping Resin with Ant > > Am 25.02.2004 um 07:38 schrieb Vincent Massol: > >> -Original Message- > >> From: Matt Raible [mailto:[EMAIL PROTECTED] > >> Sent: 25 February 2004 02:03 > >> To: Cactus Users List > >> Subject: Re: Starting/Stopping Resin with Ant > >> > >> From: > >> http://www.mail-archive.com/[EMAIL PROTECTED]/ > >> msg04762.html > >> > >> > >> Yes, I'd also like that we add / Ant > >> tasks for starting/stopping containers. It should be very easy to > >> implement as we're already doing it in the task. We could > >> probably even reuse the existing <[container name]> nested elements > >> (they're already Ant task in their implementation I think), and simply > >> add an "action" attribute (action="start|stop"). Anyone wishing to > >> help? > >> > > [snip] > > > 4/ I'm not too sure to implement the feature. The best solution is > > probably to create a startcontainer/stopcontainer tasks (or a single > > task with an action attribute) in o.a.c.i.a package and let it > > accept a nested AbstractContainer element. The other option would be to > > directly try to reuse the existing container elements as top level Ant > > tasks but adding to them an action attribute (action="start|stop"). It > > may require other attributes. The first solution is probably cleaner. > > I believe we already have this functionality in > (although not documented): > > > > > >Here we go > > > > > But you'll have to implement the start.resin goal no? It's not calling the o.a.c.i.a.c.resin.* classes , right? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Starting/Stopping Resin with Ant
Am 25.02.2004 um 07:38 schrieb Vincent Massol: -Original Message- From: Matt Raible [mailto:[EMAIL PROTECTED] Sent: 25 February 2004 02:03 To: Cactus Users List Subject: Re: Starting/Stopping Resin with Ant From: http://www.mail-archive.com/[EMAIL PROTECTED]/ msg04762.html Yes, I'd also like that we add / Ant tasks for starting/stopping containers. It should be very easy to implement as we're already doing it in the task. We could probably even reuse the existing <[container name]> nested elements (they're already Ant task in their implementation I think), and simply add an "action" attribute (action="start|stop"). Anyone wishing to help? [snip] 4/ I'm not too sure to implement the feature. The best solution is probably to create a startcontainer/stopcontainer tasks (or a single task with an action attribute) in o.a.c.i.a package and let it accept a nested AbstractContainer element. The other option would be to directly try to reuse the existing container elements as top level Ant tasks but adding to them an action attribute (action="start|stop"). It may require other attributes. The first solution is probably cleaner. I believe we already have this functionality in (although not documented): Here we go Cheers, Chris -- Christopher Lenz /=/ cmlenz at gmx.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Starting/Stopping Resin with Ant
> -Original Message- > From: Matt Raible [mailto:[EMAIL PROTECTED] > Sent: 25 February 2004 02:03 > To: Cactus Users List > Subject: Re: Starting/Stopping Resin with Ant > > From: > http://www.mail-archive.com/[EMAIL PROTECTED]/ > msg04762.html > > > Yes, I'd also like that we add / Ant > tasks for starting/stopping containers. It should be very easy to > implement as we're already doing it in the task. We could > probably even reuse the existing <[container name]> nested elements > (they're already Ant task in their implementation I think), and simply > add an "action" attribute (action="start|stop"). Anyone wishing to help? > > > I'm willing to help, but I wouldn't know where to start. Point me in > the right direction (a high-level task list would be fine) and I'll see > what I can do. Very cool! Here are some informations: 1/ the code is located in CVS in jakarta-cactus/integration/ant/src/java and jakarta-cactus/integration/ant/src/test. 2/ the Ant tasks themselves (e.g. CactusTask) are in the o.a.c.integration.ant package. 3/ the nested container elements , etc are located in o.a.c.i.a.container.* 4/ I'm not too sure to implement the feature. The best solution is probably to create a startcontainer/stopcontainer tasks (or a single task with an action attribute) in o.a.c.i.a package and let it accept a nested AbstractContainer element. The other option would be to directly try to reuse the existing container elements as top level Ant tasks but adding to them an action attribute (action="start|stop"). It may require other attributes. The first solution is probably cleaner. Let me know if you need more guidance. Thanks -Vincent > > Thanks, > > Matt > > On Feb 24, 2004, at 5:42 PM, Matt Raible wrote: > > > Thanks for the link Vincent. To be honest, I'd rather use the > > task since I know that works, and I can use that for Cactus > > tests. But for running my JSP tests (with Canoo's webtest), I start > > tomcat, run the tests, and then stop it. I'm trying to do the same > > thing for resin and then have an ant property that allows users to > > easily switch between tomcat and resin. > > > > Here's what I have. The start.resin target works fine, but the > > stop.resin target just hangs (when called in ). > > > > > > > > > > > description="starts resin in current console window"> > > > > > > > > > value="-Djava.util.logging.manager=com.caucho.log.LogManagerImpl"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > value="-Djava.util.logging.manager=com.caucho.log.LogManagerImpl"/> > > > > > > > > > > > > > > > > > > Also, I like the task, but I can't use it to test both Tomcat > > and Resin back-to-back. If I could use between the two - > > that'd be awful slick. ;-) > > > > Matt > > > > > > On Feb 24, 2004, at 10:08 AM, Vincent Massol wrote: > > > >> Hi Matt, > >> > >> So you'd like to start/stop Resin manually instead of using the > >> / nested element of the task? > >> > >> If so, you can use the following as a template: > >> http://cvs.apache.org/viewcvs.cgi/jakarta-cactus/integration/ant/src/ > >> scr > >> ipts/share/build-tests-resin2x.xml?rev=1.6&view=auto (it's for Resin > >> 2.x). FYI, that's the old scripts we were using before we migrated to > >> the task. > >> > >> Thanks > >> -Vincent > >> > >>> -Original Message- > >>> From: Matt Raible [mailto:[EMAIL PROTECTED] > >>> Sent: 24 February 2004 17:34 > >>> To: Cactus Users List > >>> Subject: Starting/Stopping Resin with Ant > >>> > >>> Is it possible to re-write the following two targets to start/stop > >>> Resin instead of Tomcat? > >>> > >>> > >>> > >>> > >>> >>> description="starts tomcat in the current console window"> > >>> >>> fork="yes&q
Re: Starting/Stopping Resin with Ant
From: http://www.mail-archive.com/[EMAIL PROTECTED]/ msg04762.html Yes, I'd also like that we add / Ant tasks for starting/stopping containers. It should be very easy to implement as we're already doing it in the task. We could probably even reuse the existing <[container name]> nested elements (they're already Ant task in their implementation I think), and simply add an "action" attribute (action="start|stop"). Anyone wishing to help? I'm willing to help, but I wouldn't know where to start. Point me in the right direction (a high-level task list would be fine) and I'll see what I can do. Thanks, Matt On Feb 24, 2004, at 5:42 PM, Matt Raible wrote: Thanks for the link Vincent. To be honest, I'd rather use the task since I know that works, and I can use that for Cactus tests. But for running my JSP tests (with Canoo's webtest), I start tomcat, run the tests, and then stop it. I'm trying to do the same thing for resin and then have an ant property that allows users to easily switch between tomcat and resin. Here's what I have. The start.resin target works fine, but the stop.resin target just hangs (when called in ). description="starts resin in current console window"> Also, I like the task, but I can't use it to test both Tomcat and Resin back-to-back. If I could use between the two - that'd be awful slick. ;-) Matt On Feb 24, 2004, at 10:08 AM, Vincent Massol wrote: Hi Matt, So you'd like to start/stop Resin manually instead of using the / nested element of the task? If so, you can use the following as a template: http://cvs.apache.org/viewcvs.cgi/jakarta-cactus/integration/ant/src/ scr ipts/share/build-tests-resin2x.xml?rev=1.6&view=auto (it's for Resin 2.x). FYI, that's the old scripts we were using before we migrated to the task. Thanks -Vincent -Original Message- From: Matt Raible [mailto:[EMAIL PROTECTED] Sent: 24 February 2004 17:34 To: Cactus Users List Subject: Starting/Stopping Resin with Ant Is it possible to re-write the following two targets to start/stop Resin instead of Tomcat? Thanks, Matt - 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: Starting/Stopping Resin with Ant
Thanks for the link Vincent. To be honest, I'd rather use the task since I know that works, and I can use that for Cactus tests. But for running my JSP tests (with Canoo's webtest), I start tomcat, run the tests, and then stop it. I'm trying to do the same thing for resin and then have an ant property that allows users to easily switch between tomcat and resin. Here's what I have. The start.resin target works fine, but the stop.resin target just hangs (when called in ). description="starts resin in current console window"> Also, I like the task, but I can't use it to test both Tomcat and Resin back-to-back. If I could use between the two - that'd be awful slick. ;-) Matt On Feb 24, 2004, at 10:08 AM, Vincent Massol wrote: Hi Matt, So you'd like to start/stop Resin manually instead of using the / nested element of the task? If so, you can use the following as a template: http://cvs.apache.org/viewcvs.cgi/jakarta-cactus/integration/ant/src/ scr ipts/share/build-tests-resin2x.xml?rev=1.6&view=auto (it's for Resin 2.x). FYI, that's the old scripts we were using before we migrated to the task. Thanks -Vincent -Original Message- From: Matt Raible [mailto:[EMAIL PROTECTED] Sent: 24 February 2004 17:34 To: Cactus Users List Subject: Starting/Stopping Resin with Ant Is it possible to re-write the following two targets to start/stop Resin instead of Tomcat? Thanks, Matt - 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: Starting/Stopping Resin with Ant
Hi Matt, So you'd like to start/stop Resin manually instead of using the / nested element of the task? If so, you can use the following as a template: http://cvs.apache.org/viewcvs.cgi/jakarta-cactus/integration/ant/src/scr ipts/share/build-tests-resin2x.xml?rev=1.6&view=auto (it's for Resin 2.x). FYI, that's the old scripts we were using before we migrated to the task. Thanks -Vincent > -Original Message- > From: Matt Raible [mailto:[EMAIL PROTECTED] > Sent: 24 February 2004 17:34 > To: Cactus Users List > Subject: Starting/Stopping Resin with Ant > > Is it possible to re-write the following two targets to start/stop > Resin instead of Tomcat? > > > > >description="starts tomcat in the current console window"> > fork="yes"> > > > > > > > > > > > > > > > > fork="yes"> > > > > > > > > > > > Thanks, > > Matt > > > - > 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]
