You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Pa...@nokia.com on 2006/04/19 05:36:02 UTC
# character causes problem parsing -lib paths
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
Re: # character causes problem parsing -lib paths
Posted by Peter Reilly <pe...@gmail.com>.
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 assume that this is due to a bug with java 1.3 which
was fixed for java 1.4. I am not too sure if ant can
work-around this issue.
On 5/10/06, Paul.Mackay@nokia.com <Pa...@nokia.com> wrote:
>
> 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 <Pa...@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
>
>
RE: # character causes problem parsing -lib paths
Posted by Pa...@nokia.com.
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 <Pa...@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
RE: # character causes problem parsing -lib paths
Posted by Matt Benson <gu...@yahoo.com>.
--- Paul.Mackay@nokia.com wrote:
> 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.
We have recently begun discussing a release of Ant
1.7. Any user who wants to try out SVN HEAD, or a
release candidate when one is available, would only be
protecting his own future productivity by aiding the
effort of testing Ant in the wild.
-Matt
>
> cheers
>
> paul
>
> >-----Original Message-----
> >From: ext Peter Reilly
> [mailto:peter.kitt.reilly@gmail.com]
> >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, Paul.Mackay@nokia.com
> <Pa...@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
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
RE: # character causes problem parsing -lib paths
Posted by Pa...@nokia.com.
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:peter.kitt.reilly@gmail.com]
>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, Paul.Mackay@nokia.com <Pa...@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
Re: # character causes problem parsing -lib paths
Posted by Peter Reilly <pe...@gmail.com>.
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 <Pa...@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
>
>