ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <Paul.Mac...@nokia.com>
Subject RE: # character causes problem parsing -lib paths
Date Tue, 09 May 2006 23:18:19 GMT
Hello,

I have tested an SVN snapshot of Ant with the fix in for parsing # in
the path. It works using Java 1.4.2 but not Java 1.3.1. My understanding
is that 1.3 is intended to be supported for Ant 1.7 based on this page
http://wiki.apache.org/ant/Ant17/Planning. Is it possible to test this
functionality using 1.3?

thanks

paul

>-----Original Message-----
>From: ext Peter Reilly [mailto:peter.kitt.reilly@gmail.com] 
>Sent: Wednesday, April 19, 2006 3:52 AM
>To: Ant Developers List
>Subject: Re: # character causes problem parsing -lib paths
>
>I have just checked.
>This is a problem - the ant launcher code does some conversion 
>of file names to URLs. The '#' character is not converted The 
>only work-around (at the moment) is to use symbolic links.
>I have made a change to ant SVN to fix this.
>
>Peter
>
>On 4/19/06, Paul.Mackay@nokia.com <Paul.Mackay@nokia.com> wrote:
>>
>> Hello,
>>
>> I have found that if I specify a -lib option with a path 
>that contains 
>> a hash "#" character, it cannot find the libraries. Without the # 
>> character in the path they can be picked up fine.
>>
>> This is not easily avoided in our environment, as we use Synergy for 
>> SCM, which defaults to using # in the path when checking out 
>projects.
>> This can be changed, but that is not desirable.
>>
>> Is this a known bug? Does anyone know of any workarounds?
>>
>> Many thanks
>>
>> paul
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message