Hi Peter, >I have made a change to ant SVN to fix this.
So if I wanted to get a version of Ant with it fixed I could check it out from SVN? Is there any bug fix release schedule for Ant? I'm wondering because there has not been a new release for some time. cheers paul >-----Original Message----- >From: ext Peter Reilly [mailto:[EMAIL PROTECTED] >Sent: 19 April 2006 03:52 >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, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]