>>Just a question have I missed a vote dropping JDK 1.2???
>>I found a discussion about that [1], but
>>- that was not a vote
>>- had some points keeping 1.2
>>
>I don't think there was a vote, as you say just a discussion
>which eventually withered without resolution
Then I'll change the wi
[EMAIL PROTECTED] wrote:
Just a question have I missed a vote dropping JDK 1.2???
I found a discussion about that [1], but
- that was not a vote
- had some points keeping 1.2
I don't think there was a vote, as you say just a discussion which
eventually withered without resolution
K
Reilly [mailto:[EMAIL PROTECTED]
>Gesendet: Mittwoch, 10. Mai 2006 12:33
>An: Ant Developers List
>Betreff: Re: # character causes problem parsing -lib paths
>
>I have just tested with java 1.3. and indeed # does not work
>there. I have not looked into this too much, but can only
&
o test this
functionality using 1.3?
thanks
paul
>-Original Message-
>From: ext Peter Reilly [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, April 19, 2006 3:52 AM
>To: Ant Developers List
>Subject: Re: # character causes problem parsing -lib paths
>
>I have just checke
functionality using 1.3?
thanks
paul
>-Original Message-
>From: ext Peter Reilly [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, April 19, 2006 3:52 AM
>To: Ant Developers List
>Subject: Re: # character causes problem parsing -lib paths
>
>I have just checked.
>Thi
in the wild.
-Matt
>
> 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
>
---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 fi
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 PRO
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
