Re: svn commit: r416276 - /ant/core/trunk/lib/optional/.cvsignore

2006-06-22 Thread Antoine Levy-Lambert
This did not work as expected. Should we rename the .cvsignore files to .svnignore ? Or are we supposed to enter a line in .$HOME/.subversion/config to say we want to use .cvsignore instead ? Regards, Antoine [EMAIL PROTECTED] wrote: > Author: antoine > Date: Wed Jun 21 23:57:29 2006 > New Rev

svn commit: r416289 - in /ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit: LogCapturer.java PlainAntUnitListener.java

2006-06-22 Thread kevj
Author: kevj Date: Thu Jun 22 00:15:53 2006 New Revision: 416289 URL: http://svn.apache.org/viewvc?rev=416289&view=rev Log: remove unused imports change year Modified: ant/antlibs/antunit/trunk/src/main/org/apache/ant/antunit/LogCapturer.java ant/antlibs/antunit/trunk/src/main/org/apache

AW: svn commit: r416276 - /ant/core/trunk/lib/optional/.cvsignore

2006-06-22 Thread Jan.Materne
>Should we rename the .cvsignore files to .svnignore ? > >Or are we supposed to enter a line in >.$HOME/.subversion/config to say we want to use .cvsignore instead ? I would go the "clean svn way". If using a .cvsignore and a redirect is often used (and not only for historical reasons) we can do

[EMAIL PROTECTED]: Project svn-antlib-test (in module ant-antlibs) failed

2006-06-22 Thread Gump Integration Build
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project svn-antlib-test has an issue affecting its community integration. This issue affe

using multiple properties in the 'if' and 'unless' conditions

2006-06-22 Thread Paul.Mackay
Hello, Has the possibility of adding multiple conditions to the target 'if' and 'unless' attributes ever been considered? Are there any reasons why this change would be a bad idea? cheers paul

Re: using multiple properties in the 'if' and 'unless' conditions

2006-06-22 Thread Dominique Devienne
It's believed that you can easily combine the various conditions in one , that sets a single property based on as complex a logic as 's nested / allows, so it's not necessary. When you remember that targets listed in 'depends' are executed before 'if' / 'unless' are evaluated, you can easily exec

svn commit: r416510 - in /ant/core/trunk: ./ lib/optional/ proposal/ant-site/anakia/ proposal/sandbox/antunit/ proposal/sandbox/dotnet/ proposal/sandbox/input/ proposal/sandbox/svn/ src/etc/testcases/

2006-06-22 Thread antoine
Author: antoine Date: Thu Jun 22 16:31:06 2006 New Revision: 416510 URL: http://svn.apache.org/viewvc?rev=416510&view=rev Log: renaming the .cvsignore files into .svnignore Added: ant/core/trunk/.svnignore - copied unchanged from r416241, ant/core/trunk/.cvsignore ant/core/trunk/lib

.cvsignore ===> .svnignore

2006-06-22 Thread Antoine Levy-Lambert
I have renamed all the .cvsignore into .svnignore and committed my change. Did not get prompted for a commit message. The question is also : in lib/optional, the file .svn/dir-prop-base did not change. $ cat dir-prop-base K 10 svn:ignore V 19 jdepend*.jar s*.jar END So most of my optional jars a

Re: .cvsignore ===> .svnignore

2006-06-22 Thread Brett Porter
.svnignore doesn't do anything. The svn:ignore properties would have been populated from .cvsignore when the repository was first converted, but after that those files can be removed. To edit the property, use: svn propedit svn:ignore . Then commit that change. Cheers, Brett On 23/06/06, Anto

Re: using multiple properties in the 'if' and 'unless' conditions

2006-06-22 Thread Stefan Bodewig
On Thu, 22 Jun 2006, Paul Mackay <[EMAIL PROTECTED]> wrote: > Has the possibility of adding multiple conditions to the target 'if' > and 'unless' attributes ever been considered? Yes, but it hasn't come up often after Ant 1.4 ;-) > Are there any reasons why this change would be a bad idea? One