Thanks. That works like a charm. My problem was that I was putting globmapper
outside of my copy task. :)
> From: bode...@apache.org
> To: user@ant.apache.org
> Subject: Re: Filemapper or globmapper
> Date: Tue, 2 Mar 2010 06:03:46 +0100
>
> On 2010-03-01, Rez P wrote
I would like to copy files with certain extensions (normally the destination
environment is used to determine the file extension) to a location and strip
off the extensions. But I currently resort to using the copy tasks with the
file and tofile attributes to accomplish this as in the example b
When your batch file is invoked all variables declared by the set command will
not get passed to the 2nd instance of the dos/command window. You have to play
around with command /c to get this to work.
Other alternatives:
Option 1:
If you're on a Windows machine, declare all the variable
27;s WEB-INF.
> I looked at the examples in the manual, but maybe I am missing something...
>
> On Thu, Feb 11, 2010 at 7:56 PM, Rez P wrote:
>
> >
> > Check out the Ant manual, it has some examples. In the excerpt below, all
> > you have to do in the war task is to ch
Check out the Ant manual, it has some examples. In the excerpt below, all you
have to do in the war task is to change the location or path of the webxml
attribute. If the web.xml is outside of your project in a higher heirachy than
your project, all you have to do is to type the absolute path,
You could always hard code user.home=c:\docume~1\rest\of\the\path to avoid
spaces
> From: quessev...@abaksystemes.fr
> To: user@ant.apache.org
> Subject: Re: Problem with javac target on Windows server
> Date: Wed, 10 Feb 2010 17:37:19 +0100
>
> >"SB" == Stefan Bodewig a écrit :
>
> Thanks f
I'm not sure if there're any other reasons but to me it's very obvious so one
can distinguish
${HOMEPATH} vs. ${env.HOMEPATH} as they're clearly 2 different animals, if you
will. How else Ant would know what you mean and how're you magically going to
reference the system environment w/o "env
In short, no. You can test it for yourself by writing a simple ant script. All
system environment variables have to be preceded by "env.", otherwise, in the
example below ${HOMEPATH} by itself is meaningless unless you have assigned a
prior value to it. But the minute it's preceded by "env." i
Here's the rule for naming targets:
A target name can be any alphanumeric string valid in the encoding of the XML
file. The empty string "" is in this set, as is comma "," and space " ". Please
avoid using these, as they will not be supported in future Ant versions because
of all the confus
I don't the reason but I do know that you cannot have spaces in target names!
Your target name should have underscores or dashes or other characters instead
of spaces:
NOT: Date: Mon, 28 Dec 2009 10:33:59 +0100
> From: reno.rkc...@free.fr
> To: user@ant.apache.org
> Subject: Re: running she
8-<---8-<
>
>
> file ./includes.staging
> ---8-<---8-<---8-<---8-<---8-<---8-<---8-<---8-<
> file*.staging
> ---8-<---8-<---8-<---8-<---8-<-------8-<---8-<---8-<
>
Hi
I need help for what I need to do and not sure how to do it. I have bunch of
property files with different extensions,
file1.{qa,staging,prod.uk,prod.us,prod.nz} and file2.{qa,staging,prod} and
file3.{qa,staging,prod}.
I need to have the copy task copy the correct respective environment
gt; Total time: 1 second
> # tar tvf DIST/ShellScripts.tar
> -rw-r--r-- 0/0 6 2009-10-15 13:37:50 alpha.txt
>
> Note the first run the tar file had foo.txt in it...
>
> Second run it correctly contained alpha.txt :)
>
>
> On Wed, 14 Oct 2009, Rez P wrote:
>
>
: f...@one2team.com
> To: user@ant.apache.org
>
> On Thu, Oct 15, 2009 at 00:48, Rez P wrote:
> >
> > Hello Everyone,
> >
> >
> >
> > How do I get the tar task to overwrite its previously created tar file?
> > Please see my current target below
Hello Everyone,
How do I get the tar task to overwrite its previously created tar file? Please
see my current target below. I don't want to delete my dist folder each time
and I don't see any options in the help section to overwrite the previous
version of ShellScripts.tar.
quot;Cross-Compilation Example" at the bottom of this page:
>
> http://java.sun.com/javase/6/docs/technotes/tools/windows/javac.html
>
> Dale
>
>
> On Thu, Jul 30, 2009 at 9:01 AM, Rez P wrote:
> >
> > Thanks for all your help and input.
> >
> >
Thanks for all your help and input.
> To: user@ant.apache.org
> Subject: Re: Building with JDK 1.3. Which version of ANT?
> From: bode...@apache.org
> Date: Thu, 30 Jul 2009 12:11:45 +0200
>
> On 2009-07-30, Rez P wrote:
>
> > I just got a successful build by
> Date: Thu, 30 Jul 2009 06:35:20 +0200
>
> On 2009-07-30, Rez P wrote:
>
> > I'm going back in time and have to compile and old java project with
> > JDK 1.3. Currently I'm using Ant 1.7 and JDK 1.5 for all my
> > projects. So when I wrote a build.xml for
Hi
I'm going back in time and have to compile and old java project with JDK 1.3.
Currently I'm using Ant 1.7 and JDK 1.5 for all my projects. So when I wrote a
build.xml for the jdk 1.3 code and in the compile target, using javac ant task,
and set the 'source' or 'target' attributes to 1.3
What's the right way to use token replacement for my Ant builds?
We have a few files common to all environments and currently maintain a set of
these files per environment -- xml files, property files, and a web.xml per
environment not identical. The files contain mostly static information ex
20 matches
Mail list logo
