You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Wellie W. Chao" <wc...@caraveltech.com> on 2002/04/05 14:51:16 UTC
Good process for develop/build/deploy/test cycle
I started using JBoss with Tomcat a few weeks ago doing development with
Struts and Tiles and find that I spend a lot of time in the deploy portion
of the application development process waiting for an EAR to deploy, which
dramatically slows down development since the build/deploy/test parts of the
cycle happen fairly frequently. Do people have recommendations on tools and
processes to speed up the cycle? It's a somewhat general question, but I
thought that developers using Tomcat might have some good advice on how to
develop efficiently.
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
RE: Good process for develop/build/deploy/test cycle
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Fri, 5 Apr 2002, Wellie W. Chao wrote:
> Date: Fri, 5 Apr 2002 09:49:36 -0500
> From: Wellie W. Chao <wc...@caraveltech.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: RE: Good process for develop/build/deploy/test cycle
>
> Yep, I use Ant, and it's great. It would really suck if I didn't. Right now
> the part that is time-consuming is waiting for the app server to deploy the
> generated EAR. I am just wondering if people use Mock Objects, Cactus, or
> something completely different that allows one to just recompile the classes
> and JSPs that have changed and immediately run what you want to test.
>
The HEAD branch (and nightly builds) of Tomcat 4 have some additions that
cater to exactly this cycle -- custom Ant tasks that interact with the
Manager webapp. My app development cycle is now:
1) Start Tomcat if it is not already running
2) ant install (Tell Tomcat where my app is)
3) ant compile (Output directly to the installed directory)
4) ant reload (If I changed a class - JSP changes picked up
automatically in the usual way)
5) test my app
6) fix something
7) goto (3).
8) ant remove (Finally, tell Tomcat I am done)
The time taken by the reload step depends on what your destroy() and
init() methods have to do -- for "hello, world" applications it takes less
than a second.
Of course, you don't get EJBs with this approach -- but if you can fake
the data layer with standard JavaBeans (perhaps developing the EJBs
independently), you can get the whole front end of the app developed this
way, and do the longer cycle stuff (deploying an EAR) only at the end.
Craig
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
RE: Good process for develop/build/deploy/test cycle
Posted by "Wellie W. Chao" <wc...@caraveltech.com>.
Yep, I use Ant, and it's great. It would really suck if I didn't. Right now
the part that is time-consuming is waiting for the app server to deploy the
generated EAR. I am just wondering if people use Mock Objects, Cactus, or
something completely different that allows one to just recompile the classes
and JSPs that have changed and immediately run what you want to test.
-----Original Message-----
From: Gregor Kovae [mailto:gregor.kovac@mikropis.si]
Sent: Friday, April 05, 2002 8:01 AM
To: Tomcat Users List
Subject: Re: Good process for develop/build/deploy/test cycle
Hi!
I've heard of people using ant to do this, but I'm sorry I cannot provide
you with more info since I'm not using it.
Sorry..
Best regards,
Kovi
At 07:51 5.4.2002 -0500, you wrote:
>I started using JBoss with Tomcat a few weeks ago doing development with
>Struts and Tiles and find that I spend a lot of time in the deploy portion
>of the application development process waiting for an EAR to deploy, which
>dramatically slows down development since the build/deploy/test parts of
the
>cycle happen fairly frequently. Do people have recommendations on tools and
>processes to speed up the cycle? It's a somewhat general question, but I
>thought that developers using Tomcat might have some good advice on how to
>develop efficiently.
>
>
>--
>To unsubscribe: <ma...@jakarta.apache.org>
>For additional commands: <ma...@jakarta.apache.org>
>Troubles with the list: <ma...@jakarta.apache.org>
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
Re: Good process for develop/build/deploy/test cycle
Posted by Gregor Kovaè <gr...@mikropis.si>.
Hi!
I've heard of people using ant to do this, but I'm sorry I cannot provide
you with more info since I'm not using it.
Sorry..
Best regards,
Kovi
At 07:51 5.4.2002 -0500, you wrote:
>I started using JBoss with Tomcat a few weeks ago doing development with
>Struts and Tiles and find that I spend a lot of time in the deploy portion
>of the application development process waiting for an EAR to deploy, which
>dramatically slows down development since the build/deploy/test parts of the
>cycle happen fairly frequently. Do people have recommendations on tools and
>processes to speed up the cycle? It's a somewhat general question, but I
>thought that developers using Tomcat might have some good advice on how to
>develop efficiently.
>
>
>--
>To unsubscribe: <ma...@jakarta.apache.org>
>For additional commands: <ma...@jakarta.apache.org>
>Troubles with the list: <ma...@jakarta.apache.org>
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>