Re: regexp-type doesn't work as expected/(advertised?)

2009-10-22 Thread Francis GALIEGUE
On Wed, Oct 21, 2009 at 08:33, Stefan Bodewig wrote: [...] > >> I then suggest that the documentation be reviewed to say that the >> regex must match all the filename. > > This is not really true, it doesn't matter whether the match is all of > the file name or only part of it, the key is that the

Re: regexp-type doesn't work as expected/(advertised?)

2009-10-20 Thread Stefan Bodewig
On 2009-10-16, Francis GALIEGUE wrote: > On Fri, Oct 16, 2009 at 06:20, Stefan Bodewig wrote: > [...] >>> Err, so what? A regex isn't supposed to match its whole input! >> Not in general, but what I described is how the regex mapper works and >> how it is documented to work.  The target file n

Re: regexp-type doesn't work as expected/(advertised?)

2009-10-16 Thread Francis GALIEGUE
On Fri, Oct 16, 2009 at 06:20, Stefan Bodewig wrote: [...] > >> Err, so what? A regex isn't supposed to match its whole input! > > Not in general, but what I described is how the regex mapper works and > how it is documented to work.  The target file name is constructed from > the to pattern exclu

Re: regexp-type doesn't work as expected/(advertised?)

2009-10-15 Thread Stefan Bodewig
On 2009-10-12, Francis GALIEGUE wrote: > On Mon, Oct 12, 2009 at 07:00, Stefan Bodewig wrote: >> On 2009-10-09, Francis GALIEGUE wrote: >>> >>>         >>>                 >>>                         >>>                         >>>                 >>>         >> means map anything tha

Re: regexp-type doesn't work as expected/(advertised?)

2009-10-12 Thread Francis GALIEGUE
On Mon, Oct 12, 2009 at 08:40, Francis GALIEGUE wrote: [...] > > Let me be more precise about that. > > If I: > > echo t.xml | sed 's,xml$,txt' > > I get t.txt as an output. As expected. > > I know that Java's .matches() method on a String is a misnomer (it > tries and matches the whole input, unl

Re: regexp-type doesn't work as expected/(advertised?)

2009-10-11 Thread Francis GALIEGUE
On Mon, Oct 12, 2009 at 08:26, Francis GALIEGUE wrote: > On Mon, Oct 12, 2009 at 07:00, Stefan Bodewig wrote: >> On 2009-10-09, Francis GALIEGUE wrote: >> >>> >> >>>         >>>                 >>>                         >>>                         >>>                 >>>         >> >> m

Re: regexp-type doesn't work as expected/(advertised?)

2009-10-11 Thread Francis GALIEGUE
On Mon, Oct 12, 2009 at 07:00, Stefan Bodewig wrote: > On 2009-10-09, Francis GALIEGUE wrote: > >> > >>         >>                 >>                         >>                         >>                 >>         > > means map anything that ends with "xml" to "txt" - no prefix here. > E

Re: regexp-type doesn't work as expected/(advertised?)

2009-10-11 Thread Stefan Bodewig
On 2009-10-09, Francis GALIEGUE wrote: > > > > > > > means map anything that ends with "xml" to "txt" - no prefix here. > Say that t.txt doesn't exist. The first time the file is run, then it

regexp-type doesn't work as expected/(advertised?)

2009-10-09 Thread Francis GALIEGUE
Hello, Take this example: bu...@build ~ $ cat build.xml Say that t.txt doesn't exist. The first time the file is run, then it is created. So far

Re: junittask includeantruntime attribute doesn't work as expected

2008-12-28 Thread metcox
It make sense, but does the purpose of the includeantruntime attribute to include or not the ant libraries on the classpath? It seems it does. But why I still have the warning? And I have the same kind of warning if I use ant 1.7.1 dependencies, but in this last case the junit test works. Regards,

Re: junittask includeantruntime attribute doesn't work as expected

2008-12-28 Thread Peter Reilly
You cannot use ant 1.7 with ant 1.6 jars. The ant 1.7 junit task is expecting ant 1.7 jars. Peter On Sun, Dec 28, 2008 at 2:59 PM, metcox wrote: > Hi, > > I'm trying to use junittask with fork mode on, on a project with ant > dependencies. > So I set includeantruntime to false and fork to true

junittask includeantruntime attribute doesn't work as expected

2008-12-28 Thread metcox
Hi, I'm trying to use junittask with fork mode on, on a project with ant dependencies. So I set includeantruntime to false and fork to true but I have conflicts. I'm working with java 1.6.0_10 and ant 1.7.1 and I'm getting the following output: [junit] WARNING: multiple versions of ant de

RE: doesn't work as expected

2005-09-07 Thread Rebhan, Gilbert
pected now. Gilbert -Original Message- From: Ninju Bohra [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 07, 2005 6:34 PM To: Ant Users List Subject: RE: doesn't work as expected Let's start from the beginning... did you set the property ant.enable.asserts whe

RE: doesn't work as expected

2005-09-07 Thread Ninju Bohra
rking > correctly > if i need it > > Gilbert > > -Original Message- > From: Burgess, Benjamin > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 07, 2005 3:17 PM > To: Ant Users List > Subject: RE: doesn't work as expected > > An easier solu

RE: doesn't work as expected

2005-09-07 Thread Rebhan, Gilbert
y. I just wanted to know how to get assert working correctly if i need it Gilbert -Original Message- From: Burgess, Benjamin [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 07, 2005 3:17 PM To: Ant Users List Subject: RE: doesn't work as expected An easier solution would be

RE: doesn't work as expected

2005-09-07 Thread Burgess, Benjamin
An easier solution would be to pull the for loop into its own target and then add an if="your-property" to the target. Ben -Original Message- From: Rebhan, Gilbert [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 07, 2005 6:11 AM To: user@ant.apache.org Subject: doesn

doesn't work as expected

2005-09-07 Thread Rebhan, Gilbert
Hi, antcontrib 1.0b2 / ant 1.6.5 i want to use the antcontrib / assert task in my script to ensure that a for loop is only executed if a property has been set. so i have = ... in my script. Now i tested the worst case, when the property hasn't been set. But