ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject AW: AW: Default excludes and Subversion on Windows
Date Fri, 18 Aug 2006 07:13:14 GMT
If we reject automatically handling _svn directories (as a "hack" as said by svn-people), we
document it in the manual of <defaultexcludes> and svn-antlib with a reference (and
a quotation) of 
the svn statement.


>-----Urspr√ľngliche Nachricht-----
>Von: Antoine Levy-Lambert [] 
>Gesendet: Mittwoch, 16. August 2006 01:41
>An: Ant Developers List
>Betreff: Re: AW: Default excludes and Subversion on Windows
>I would also not make the behavior of defaultexcludes 
>conditional upon an environment variable. 
>I would also go to inconditionnally hardwire exclude _svn directories.
>-------- Original-Nachricht --------
>Datum: Tue, 15 Aug 2006 11:53:21 -0500
>Von: "Dominique Devienne" <>
>An: "Ant Developers List" <>
>Betreff: Re: AW: Default excludes and Subversion on Windows
>> > Accessing environment variables from Java is a hack. Do we want to
>> always
>> > execute it? In case of failure, normal build execution can be 
>> > affected,
>> even
>> > if people do not care about "_svn" directory names.
>> Not in JDK 1.5+ anymore. But I agree than fetching the env if that 
>> user hasn't explicitly done it already is a bit heavy handed.
>> I hesitate between Stefan's position of requiring the user to do it 
>> explicitly and adding it to the default excludes. Since 
>> <defaultexcludes> allows both adds and removes, I guess adding it to 
>> the hardwired defaults (unconditionally, no env fetching) would 
>> benefit more people, and Kev and others can still do an explicit 
>> <defaultexcludes remove="**/_svn/**>, although I guess a remove is 
>> trickier, since requires knowing the exact pattern to remove.
>> --DD
>To unsubscribe, e-mail: For 
>additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message