portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor" <da...@bluesunrise.com>
Subject Re: cvs commit: jakarta-jetspeed/build build.xml
Date Tue, 20 Nov 2001 17:40:54 GMT
This task only copies the classes. It doesnt attempt to copy the webapp or
any jarfiles.
Its useful for me during dev.  I prefer ant tasks that are short and simple
to remember. Thats why I chose 'deploy'. Names like 'install_all' and
'install_classes' get too long for my taste (imo)

----- Original Message -----
From: "Paul Spencer" <paulsp@apache.org>
To: "Jetspeed Developers List" <jetspeed-dev@jakarta.apache.org>
Sent: Tuesday, November 20, 2001 7:17 AM
Subject: Re: cvs commit: jakarta-jetspeed/build build.xml


> Their already is a "install" task that copies classes and jars to the
> webserver.  Is their a reason to have both the "install" and "deploy"
> tasks?  If so, then pick similar names, i.e. "install_all" and
> "install_classes"
>
> What about "install_war"?
>
> Paul Spencer
>
> taylor@apache.org wrote:
>
> > taylor      01/11/19 20:52:32
> >
> >   Modified:    build    build.xml
> >   Log:
> >   - added deploy task that simply 'hot deploys' the class files to the
webapp directory of your webserver.
> >     this is useful during development. This task will not copy the
'webapp' files such as psml, templates.
> >
> >   Revision  Changes    Path
> >   1.107     +16 -0     jakarta-jetspeed/build/build.xml
> >
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:jetspeed-dev-help@jakarta.apache.org>
>
>



--
To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>


Mime
View raw message