ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Reilly" <peter.kitt.rei...@gmail.com>
Subject Re: # character causes problem parsing -lib paths
Date Wed, 19 Apr 2006 10:51:38 GMT
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
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message