Title: Path Identifier.
Hi,
It is possible to use a path identifier defined in an XML file by another XML called by the first one, like it is possible with the properties?
In fact, I have a basic XML file that define some tasks and is called by others XML, so in each case I want to give to
Can somebody tell me where to find P4 sources (of the optional packet)
because I always get problems when running p4sync in ant. and the logging it
produces is not very vlear.
Erik
I would like to pass a site name as a command line parameter and then use it
to construct another property name.
The way to do this should be something similar to the following :
Command-line parameter: 'site_name'
Property name: 'site_name.deployment.dir'
Resulting
Title: RE: Nested properties/parameters
I think you should try like this:
Resulting property: property name=result value=${site_name}.deployment.dir/
Natalia
-Original Message-
From: Stefan Lecho [mailto:[EMAIL PROTECTED]]
Sent: 29 June 2001 13:20
To: '[EMAIL PROTECTED]'
Subject:
You can't nest properties like this, but is that what you want to do?
Seems to me you want something like:
property name=result value=${site_name}.deployment.dir/
And then you could have a properties file that defines all the
deployment directories for each site you're using:
Hi,
Is anyone aware of the existence of a Pvcs task class for Ant? A customer of ours
uses Pvcs for
source code version control and I'm using Ant to build and deploy. I would like to
include a Pvcs
target to get all the code from the Pvcs archive. I guess the Cvs class could be used
a
I'd like to package some EJBs into the same jarfile. Is it possible?
Here are the details:
I'm using ant (the optional task ejbjar) to package EJBs into jars for the
deployment in weblogic (5.1). For every EJB (only session beans) I have the
two XML descriptors, named using the task convention
Hi Les,
I finaly mad it through. To get it work I had to comment out the following 3
lines in the P4Base.java file
commandline.createArgument().setValue(P4Port);
commandline.createArgument().setValue(P4User);
commandline.createArgument().setValue(P4Client);
Is this a known feature or am I
Hi all,
i've got a property ${package.name} = my.package.name for example,
and i would like to obtain from ${package.name}
a new property ${package.path} = my/package/name
Task Replace only works with string from files ?
any ideas ?
Thanks.
Gilles.
I'll try to explain my problem more appropriate.
site.property
site_name=jakarta.apache.org
deploy.property
jakarta.apache.org.deployment.dir=html
When using deploy.property I want to get the key
'${site_name}.deployment.dir' which in this case gets resolved to
If you specify p4user p4port or p4client then p4base uses the -u -p and -c
switches to pass this info on. You do not need to comment out these lines
as, if you do not set these attributes in your xml file, p4base ignores them
and uses those specified by p4 set.
What version of client are you
I haven't read either book, but my tuppence worth is below:
Depends why you're building. If you're just doing a development build in
your own sandbox, then no, I wouldn't bother copying them. If you're
building a version for UAT or production then you want a build environment
as independent from
Hi Kyle,
1/ The build directory is called by different among projects. Some called
it build, others out,
2/ It is needed for several reasons. Regarding the copy of source files the
main reason is to apply filter tokens (filter task in Ant), like change
version in source file or date or
Perhaps I'm doing things differently than most (although I don't think so,)
but my build directory is used to hold the compiled output of the build
process. I have subdirectories underneath for segments of the build that
require separate class trees (system, ejb, test, etc) and underneath those
--- Kyle Adams [EMAIL PROTECTED] wrote:
In several of the papers I've read on using Ant (specifically Ant in
Anger and the short tutorial on Ant in the Cactus subproject), a build
directory is included in the ideal directory structure. Build, as far
as I can tell, is used a temporary holding
Stefan,
The lack of this functionality was submitted as a bug (#1733), and a task
was submitted as an attachment to the bug report. I've just picked up that
code, compiled it, and tried it:
target name=setprop
property file=deploy.property/
echo message=site_name is ${site_name}/
I don't see how you can achieve what you're after. Why do you need to
normalize all access through deploy.property? Why not simply use
${site_name}.deployment.dir?
- Don
--- Stefan Lecho [EMAIL PROTECTED] wrote:
I'll try to explain my problem more appropriate.
site.property
I have a need to replicate a single directory tree under multiple other
directories. The target directories are dynamically defined (i.e. someone
creates a new one in the right spot and it then becomes a target directory
for this replication). Before trying the controversial foreach task,
To clarify, we have in each file the following javadoc comment @version
@version@.
We also have other files, like configuration files that need a path in them.
We like to define the path in a single place (like as a property in the
build.xml file) so that when this path changes we only update it
Kyle,
I think most projects copy the files to a build directory to replace the
tokens within the files. Also, for official builds, it gives you a place
from which to archive the source that was used to create the build.
I wrote our targets to compile from the source without doing a copy first.
Hi,
The use of an array instead of a single string was a bug fix submitted by
someone a while back. I guess the reporting side wasn't updated at the same
time to reflect the change in how p4base does exec.
Diane, could you commit a patch for this?
Thanks,
Les
-Original Message-
Thanks for your reply, Diane. I have tried the
--- -logfile filename option to 'ant' ---
approach. That has provided me with the feedback that I was looking for.
Regards,
David
-Original Message-
From: Diane Holt [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 28, 2001 8:23 PM
To:
Thanks for the replies.
It appears that the main reason for copying is to filter and replace tokens. If
that's true, doesn't it make more sense to simply use the Replace task? Then, since
the filtering's been taken care of, just compile with the srcdir attribute set to your
source
One reason to use AntCall instead of depends: depends does not guarantee
the order that the targets will be executed in. Granted, the current
implementation calls them in the order they're listed, but I've seen
quite a few emails from committers saying that this could change. So if
you want to
Hari,
I believe you forgot to specify your mail host.
HTH,
Felice
-Original Message-
From: Hari Ramasubbu [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 2:35 PM
To: [EMAIL PROTECTED]
Subject: Mail api ...
I'm trying to send the build log thru' .mail
I get this error :
Looks like you haven't specified a mail host.
JP
-Original Message-
From: Hari Ramasubbu [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 12:35 PM
To: [EMAIL PROTECTED]
Subject: Mail api ...
I'm trying to send the build log thru' .mail
I get this error :
mail.xml:3: IO error
You're missing the mailhost attribute.. If you don't specify the server
to use to send the message it can't send it..
-Original Message-
From: Hari Ramasubbu [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 2:35 PM
To: [EMAIL PROTECTED]
Subject: Mail api ...
I'm trying to send
I've checked for bugzilla and mail-archive.com for reports of this issue
with no avail.
Basically, there tar task seems defunct when I run the following target
definition under these two ant distros:
Among other things, it overrides the fixcrlf applied in the previous step of
this target,
Ooops.. I sent before I was done typing my message :)
Ignore the first, and I'll fill in the blanks on this one:
-Original Message-
From: Cook, Levi
Sent: Friday, June 29, 2001 3:14 PM
To: '[EMAIL PROTECTED]'
Subject: tar task blues
I've checked for bugzilla and mail-archive.com for
On Sat, 30 Jun 2001 04:41, Kyle Adams wrote:
Was the Replace task not available in earlier versions of Ant,
yep ;)
necessitating the Copy workaround, or is there a performance advantage to
filtering via Copy rather than Replace?
and yep ;)
Replace will process filename everytime. While
On Sat, 30 Jun 2001 06:19, Cook, Levi wrote:
Ooops.. I sent before I was done typing my message :)
;)
Among other things, it overrides the fixcrlf applied in the previous step
of this target, which results in .sh scripts with DOS line terminators. :(
Can anyone confirm this behavior? or
31 matches
Mail list logo
