Try what I use:
...
Thank you,
Chuck Holzwarth
(804) 403-3478 (home)
(804) 305-4040 (cell)
- Original Message
From: Peter Reilly <[EMAIL PROTECTED]>
To: Ant Users List
Sent: Monday, June 16, 2008 7:49:42 AM
Subject: Re: Depends="init" problem
each creates a new project, targets
Thanks for the tips everyone. I've 'fixed' the build file and now
have all artifacts of ant sent to the build directory.
On Mon, Jun 16, 2008 at 12:11 PM, Vallon, Justin <[EMAIL PROTECTED]> wrote:
> Let me second that, with a further example: I would be "frustrated" if
> an "ant clean" deleted m
Let me second that, with a further example: I would be "frustrated" if
an "ant clean" deleted my scratch files, notes, etc, that might be
sitting at the top-level of a project.
-Justin
office 8-383-6725, 212-272-6725; cell 917-861-6042
-Original Message-
From: David Weintraub [mailto:[EMA
You have "src/**/*" instead of just "src/**".
I believe they both mean the same, but I can't say for certain. The
"**" means all the files in the current directory and all files in the
subdirectories too.
You can have something like this:
which will exclude all files in all directories with th
This would work.
However, it it very dangerous, it it too easy to
delete stuff that you do not wont to.
I would place *all* the generated artifacts of a build in a
special directory - "build" or "target", and for
the clean target, simply delete that directory.
Peter
On Mon, Jun 16, 2008 at 4
Hey David,
Thanks for the help. This is the final copy, and it appears to be working.
I had to add the /* to the end of the directories to get the actual
files under those d
Many of the options you list are the same that javac takes command line.
However, for refid its a refid to a classpath variable set up elsewhere in
your build script.
You might take a look at the online Ant docs w/ regards to path's and
refid's...
On Mon, 16 Jun 2008, [EMAIL PROTECTED] wro
One more thing I just noticed (bad eyesight due to staring at computer
screens for way too long), You have just "src/*" and "test/*". You
probably want "src/**" and "test/**". A single asterisk means just the
current directory. A double asterisk means all subdirectories too.
--
David Weintraub
[EM
Built a quick test myself:
This works great -- except it doesn't delete directories. Filesets
delete files, not directories. However, adding a "includeemptydirs"
parameter to the delete task seems to do the
Partially solved my own problem at this point. No longer getting
NullPointer but I still can't get the right includes. My syntax must
be off or something. Good news is that the exclude seems to be
working.
Current target contents:
Hi All,
I need to understand the meaning of following lines. I searched lot but
did not get anything. Please help.
I did not get the meaning of debug,deprecation,optimize,classpath refid
options in javac tasks.
Regards
Irfan.
Hey Everyone,
I'm trying to develop a clean target that essentially deletes
everything but a given set of files, rather than explicitly specifying
everything to delete. This seems like a slightly more elegant
solution than the alternative, but I'm having very little success at
the moment. I've i
Martin wrote:
Good Morning All-
for ANT v 1.70
what happened to ant-optional-1.5.2.jar?
I see this discontinuity when running ant
Invalid implementation version between Ant core and Ant optional tasks.
core: 1.7.0
optional: 1.5.2
Is there a different ant-optional which reconciles with AN
A properties file is a standard Java properties file...
Basically,
name = value
pairs ;)
On Mon, 16 Jun 2008, [EMAIL PROTECTED] wrote:
Hi all,
Can anyone please give me the sample build. properties file. I need to
understand the syntax of the same.
Please help
Regards
Irfan.
each creates a new project, targets in each project
are independent of targets with the same name in other projects.
Peter
On Mon, Jun 16, 2008 at 9:00 AM, Bourzeix, Hervé
<[EMAIL PROTECTED]> wrote:
> You may have antcall in your code. Antcall don't pay attention to the depends
> list.
>
> reg
In the Ivy documentation for the task, it suggests
*"Please prefer the use of retrieve + standard ant path creation, which make
your build more independent from ivy (once artifacts are properly retrieved,
ivy is not required any more)."*
Do most people follow this retrieve+ant practice? Cachepath
You may have antcall in your code. Antcall don't pay attention to the depends
list.
regards,
-Original Message-
From: Guy Catz [mailto:[EMAIL PROTECTED]
Sent: Monday, June 16, 2008 9:50 AM
To: user@ant.apache.org
Subject: Depends="init" problem
I have several targets, all depends on in
You try to read the build.properties file:
from the location that is unknown, because ${output} is not defined at
the moment the properties file is being read.
If your build.properties file is in the current directory, just use
.
-Ognjen
[EMAIL PROTECTED] wrote:
Hi,
Thank you for respo
Hi,
Thank you for response. Actually I have written one build.xml and build.
properties file but unfortunately it is not executing fine.
Build script is not compiling the actual source code and secondly it is
creating the directory as ${output}\classess instead of classess.
Please find the attach
hi,
I think the way you invoke the targets is like:
ant -f buildFile.xml a b c
If that is the case, you are invoking each target independent of each
other - which means that the dependencies for each are discovered
separately and executed - once for a, once for b and once for c. If you
had a s
[EMAIL PROTECTED] wrote:
Can anyone please give me the sample build. properties file. I need to
understand the syntax of the same.
There is nothing special about build.properties file. Just the textual
name-value pairs, someting like:
src=src
build=bin
deploy=/usl/local/tomcat/webapps
and s
Hi all,
Can anyone please give me the sample build. properties file. I need to
understand the syntax of the same.
Please help
Regards
Irfan.
That is because your tasks a,b,c are depending on Task "init"
That means before executing target a, target "init" will be executed.
same for Target b & c.
Thats why init will be executed thrice.
Thanks & Regards
Sandeep Kumar K
Sr. Software Engineer
Geneva Software Technologies Limited,
# 82, R
There are many ways to call ant targets. If you stick with using the depends
to get a target called, then ant will never duplicate a target. So to get a
target to call a then b then c but only run init once, just make this new "big"
target depend on a,b,c and it will call each of them in order
I use something like :-
and then have the four targets init, a, b and c doing whatever.
Regards
Chris
On Mon, Jun 16, 2008 at 9:50 AM, Guy Catz <[EMAIL PROTECTED]> wrote:
> I have several targets, all depends on init -
>
>
> ...
>
>
> ...
>
>
> ...
>
> and of course
> ...
>
>
> Now, I a
I have several targets, all depends on init -
...
...
...
and of course
...
Now, I also have a target which call a, then b and then c.
But when I run that ANT, the output is something like this -
running - successful
running -successful
running - successful
running -
26 matches
Mail list logo
