On 1/27/06, Brown, Carlton <[EMAIL PROTECTED]> wrote:
> The ant task seems to create zero-length output files for a few
> of my unit test classes. It does so without reporting any errors but
> of course of course chokes on them complaining about
> premature EOF.
> Does anyone have any suggestio
Or you can use the replacefilterfile='file' attribute on the task
and specify all the replacements in the 'file'.
Later,
Ninju
- Original Message
From: Ken Gentle <[EMAIL PROTECTED]>
To: Ant Users List
Sent: Friday, January 27, 2006 8:18:51 AM
Subject: Re: Expanding properties
The ant task seems to create zero-length output files for a few
of my unit test classes. It does so without reporting any errors but
of course of course chokes on them complaining about
premature EOF.
Does anyone have any suggestions as to how to troubleshoot a problem
like this?
Thanks
Why not use 'PropertyRegex' from ant-contrib ?!?
> -Original Message-
> From: Frank Henry [mailto:[EMAIL PROTECTED]
> Sent: 27 January, 2006 11:06
> To: user@ant.apache.org
> Subject: Regexp to property
>
> For a little tool I am working on I need to get information
> from a file, via
Here are the steps you should follow:
1. Get the source for Ant 1.6.5
2. Download the patch file from the bug report.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36302
3. Patch the file
src/main/org/apache/tools/ant/util/TeeOutputStream.java in the 1.6.5
source
4. build
5. Copy ant.jar from
I highly recommend using the binary distribution. Even when there is a part of
the Ant codebase that I need patched I will compile just that part and deploy
it into the binary distribution. Just my 2 cents.
-Rob Anderson
> -Original Message-
> From: Clifton Craig [mailto:[EMAIL PROTECTE
Dominique Devienne <[EMAIL PROTECTED]> wrote on 01/27/2006 10:15:24 AM:
> I never needed something like this, but why not... Note though that I
> feel you might be better served by creating a new file (a .properties
> for example) in META-INF, using a conventional name, that's very easy
> to load
> ... and the user would be able to invoke ant like this:
>$ ant -Dmanifest.Foo=bar -Dmanifest.Color=green
>
> The build.xml should find every property with the "manifest." prefix,
> ...
>Foo: Bar
>Color: Green
>
> The only thing I can think of is to use a property set like this:
>
On 1/27/06, Frank Henry <[EMAIL PROTECTED]> wrote:
> For a little tool I am working on I need to get information from a file,
> via regexp, and store it into a property.
> Before a dive into depths I have not yet ventured into, sofar I have
> only written simple tasks, I wanted to glance about if a
Untried:
HTH...
Ken
At 06:29 2006-01-27, you wrote:
Hi
Say I have a file, called contents.txt, which contains the text:
contents.txt:
The value is ${something}
And I have a property file values.properties which reads
values.propeties:
something=somev
> The only thing I can think of is to use a property set like this:
>
>
>
>
> ... and extend Manifest.java to take a propertyref id.
I think this is an excellent suggestion! You'd also have to make this work
with sections, but this is a really great idea.
If you submit a patc
Hi
Say I have a file, called contents.txt, which contains the text:
contents.txt:
The value is ${something}
And I have a property file values.properties which reads
values.propeties:
something=somevalue
How to I turn contents.txt into
contents.txt:
The value is somevalue
I can do this with
For a little tool I am working on I need to get information from a file,
via regexp, and store it into a property.
Before a dive into depths I have not yet ventured into, sofar I have
only written simple tasks, I wanted to glance about if anyone has
already written something like that.
Thanks!
St
13 matches
Mail list logo
