On 7/28/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
>
> "${stage.proj.wwwroot}" transfertype="${stage.transfertype}" />
The second deploy specifies basepath+proj.wwwroot+transfertype, when
it should not be necessary, just like in the first deploy above.
Oh, right. I saw that it
most other cases,
> it's much better to use the 'depends'
> attribute of 'target' with the exact target names.
>
> To achieve a deploy-all case, you could have a separate
> target (optimally in a separate script) that makes 'ant'
> calls into
I'm trying these things out as you folks suggest them. Your latest
suggestion meets my original requirements (fleshed out below... I'm open to
further comments), but Andrew's point about scalability is well taken, so
I'm going to make a decision based on a few factors.
Thanks again Dominque and A
;s much better to use the 'depends'
> > attribute of 'target' with the exact target names.
> >
> > To achieve a deploy-all case, you could have a separate target
(optimally in
> > a separate script) that makes 'ant' calls into the main de
akes 'ant' calls into the main deployment script:
... etc
-Andrew
On 7/28/06, Jamie Jackson <[EMAIL PROTECTED]> wrote:
>
> Thanks for the quick response. I have a couple of follow-ups.
>
> I've gotten the impression from read
envname determines which environment-specific properties file needs to
be
> read.
>
> This is a more scalable solution. Adding a new environment is as simple
as
> creating a new properties file.
>
> This assumes the build has already occurred and you can make run the
> deploymen
I'm having a problem trying to grok the "ant way" to do things (i.e.,
without conditionals). I just got started with Ant a couple days ago, so
take that into consideration.
I'm trying to produce a well-factored script to handle code deployment to
remote servers.
Tasks:
* deploy-integ
* deploy-
