If you have checked the destination directory out from subversion, you should
be able to create a target where you use the contrib var to override the
basedir property and add the file. When you return from the antcall your
basedir will revert to what it was before and you can continue your comp
Hello everyone,
I am relatively new to Ant and am trying to do an svn add as part of my
build script.
I can force svn to add recursively using the following command
"svn add * --force".
Unfortunately, I am not in the same directory that I need the add to
work on. It tries to do the add in the curr
Rob:
Yeah - that's a good point :) Pt well taken ;)
Anderson, Rob (Global Trade) wrote:
Scott, In your example the "if" part of the wrapper is redundant, since
all the depends have the same "if" attribute. It would work just the
same, but removing the "if" part of the wrapper would allow the b
I would recommend getting this information from your source control
system, if possible. If you are using CVS, you could use the
cvschangelog task. For ClearCase there is a task in the clearantlib
package that will do the same thing. For other source control systems
you may have to get creative wit
Use the -lib option when running ant. For example...
ant -lib /path/to/jars target
See the documentation for more details.
http://ant.apache.org/manual/running.html#options
-Rob Anderson
-Original Message-
From: Bourzeix, Hervé [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 12,
Scott, In your example the "if" part of the wrapper is redundant, since
all the depends have the same "if" attribute. It would work just the
same, but removing the "if" part of the wrapper would allow the build to
run some targets regardless.
Excellent example. Just adding my 2 cents,
-Rob Ander
Someone recently mentioned the antcallback task which is part of
ant-contrib. It's the same as antcall but allows properties set in the
called target to be available for use in the calling target. Maybe that
would work for you.
http://antelope.tigris.org/nonav/docs/manual/bk03ch20.html
Barry
--
Cyril:
Sorry, was on my way to bed when I responded... I probably should have
tried an example...
I think Jan pointed out something like below...
Cyril Sagan wrote:
Sc
Dmitri - Thanks for the response, but this does not work.
The problem is that state (properties) set by the target of an will
not be available to the calling environment.
I'm still looking for an elegant solution.
--Cyril
From: Dmitri Farafonov [EMAIL
Scott - Thanks for the response, but that doesn't work.
The "A,B,C,D" depends targets will be executed first, it is only the body of
"wrapper" that's conditional based on the property.
I'm still looking for an elegant solution.
--Cyril
From: Scot P. Flo
I have a master setup.xml that imports plugin specific ant files, for
example for
ant-contrib, cobutura, jaxb, axis etc. These contain typedefs to define the
plugin task, macrodefs to invoke the tasks, and targets. I also have a
common targets.xml that does things like build main, build test, run
c
11 matches
Mail list logo
