On 29/07/06, Chun Ji <[EMAIL PROTECTED]> wrote:
I want to insert a html file in my email, not an attachment.
Does someone know how to do it in ant.
-CJ
-Original Message-
From: Jamie Jackson [mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 11:31 AM
To: Ant Users List
Subject: Re:
On 29/07/06, satheesh <[EMAIL PROTECTED]> wrote:
I have written a java class which will add two values and print it in the
console and I called that class in ant as mentioned below,
how can I get that value (or returned that value from class) back to ant
target or the property tag
What's
I have written a java class which will add two values and print it in the
console and I called that class in ant as mentioned below,
how can I get that value (or returned that value from class) back to ant
target or the property tag
What's the solution for this proble?
Thanks,
satheesh
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
I want to insert a html file in my email, not an attachment.
Does someone know how to do it in ant.
-CJ
-Original Message-
From: Jamie Jackson [mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 11:31 AM
To: Ant Users List
Subject: Re: Trying to do things the "Ant way"
Importance: L
The second deploy specifies basepath+proj.wwwroot+transfertype, when
it should not be necessary, just like in the first deploy above.
deploying all
For the scalability issue, it's easy to have loop of the
value of an environments var, which would contain a comma separated
list
We have other setups that do have clustered stage and production
environments, so I'll file that one away for later. :-)
Thanks,
Jamie
On 7/28/06, Anderson, Rob (Global Trade) <[EMAIL PROTECTED]> wrote:
This is great advice, and certainly one way to do the deploy-all. I
would like to share ano
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
I think you've misunderstood what I intended the "build-all" task to mean.
I think you're right. I've misunderstood the problem. Now that I think
I do, I probably would have gone with NFS...
SSH wrapped in a . Something like:
macro deploy
attr server
attr deploy-type defaults to [EMAIL
I've translated your pseudo-code into Ant (see bottom), and I see that it
does seem to remove the need for . However, unless *I* have
misunderstood your reply, I think you've misunderstood what I intended the
"build-all" task to mean.
Each server in my case has one preferred transfer type; theref
This is great advice, and certainly one way to do the deploy-all. I
would like to share another option...
I once worked in situation where most of our environments were
clustered, having two servers per environment. In this case I would
create a "deploy-each" target, to deploy to one server, and w
Thanks... A co-working pointed out that oops after I'd sent the
email...
-Mark
This e-mail message, and any attachments, is intended only for the use of the
individual or entity identified in the alias address of this message and may
contain information that is confidential, privileged and
Not really enough information here. Please send the portion of your
build.xml and the ouput when you run Ant. Also, specify the version of
Ant and Jsch, as well as the FTP and/or ssh server distribution and
version you are running on windows.
-Rob A
> -Original Message-
> From: Venkatesh
One needs to use .* for regular expressions.
Peter
On 7/28/06, Mark Modrall <[EMAIL PROTECTED]> wrote:
Hi...
I'm trying to filter the output from an svn update to get
the version number it's up to. I want to grab just the version number
and output that to a file. I've been exp
BTW, in -deploy-all, I usually set these properties as
To emphasis the fact that it's the properties existence that matters,
not it's value (because that's what target's if/unless check). --DD
On 7/28/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
You can do something like:
target deploy-
You can do something like:
target deploy-A if "deploy-type==A"
target deploy-B if "deploy-type==B"
target deploy depends -check-deploy, deploy-A, deploy-B, etc...
target deploy-all depends -deploy-all, deploy
target -check-deploy
condition ${deploy-type} equals "A" set property "deploy-type==A
Okay, thanks a lot. I'll give it a shot. :-D
Thanks,
Jamie
On 7/28/06, Andrew Goktepe <[EMAIL PROTECTED]> wrote:
There is a loss of performance when you use antcall in large,
complex builds. It also makes target dependencies less clear. But it's the
only way I know of to call a specific target
There is a loss of performance when you use antcall in large,
complex builds. It also makes target dependencies less clear. But it's the
only way I know of to call a specific target based on a value obtained at
runtime. In most other cases, it's much better to use the 'depends'
attribute of 'targe
Thanks for the quick response. I have a couple of follow-ups.
I've gotten the impression from reading other posts that is to be
avoided, so I'm wondering about its use here.
The other question I have is: How would I satisfy the deploy-all use case
while reusing as much of the script as practica
Oops. s/ wrote:
We use a separate properties file for each environment, and have common
property names. Instead of integ.transfertype, stage.transfertype, etc, I
would just have 'transfertype' and it would have different values in the
different files. Then the Ant script has targets based on th
We use a separate properties file for each environment, and have common
property names. Instead of integ.transfertype, stage.transfertype, etc, I
would just have 'transfertype' and it would have different values in the
different files. Then the Ant script has targets based on the possible
values o
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-
Hi...
I'm trying to filter the output from an svn update to get
the version number it's up to. I want to grab just the version number
and output that to a file. I've been experimenting with on
but I'm running into some odd things (at least from what I can
tell out of the documen
I updated the note [1] (revision 426479).
Thanks for pointing out.
Jan
[1]
http://svn.apache.org/repos/asf/ant/core/trunk/docs/manual/CoreTasks/war.html
>-Ursprüngliche Nachricht-
>Von: Master, Tariq (Abbeywood) [mailto:[EMAIL PROTECTED]
>Gesendet: Mittwoch, 26. Juli 2006 17:31
>An:
James Adams wrote:
I am running some JUnit tests through Ant's junit task, and I am hoping
to be able to filter out most of the exceptions which are currently
displayed in the failure reports. I have set filtertrace="on", but this
appears to be the default and it makes no difference. Essentia
With Ant 1.7 (after HackathonEU 2005) is also a Resource-Selector.
So a
should be possible.
Jan
>-Ursprüngliche Nachricht-
>Von: Michael Giroux [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 25. Juli 2006 17:58
>An: Ant Users List
>Betreff: Re: for refid
>
>Dominique,
>
>On
26 matches
Mail list logo