Tom,
Ant tries to be very accommodating with regard to paths. So it will try to
interpret paths using both : or ;. Also paths may be put together with
fragments from different systems.
As an example, say you have the following
<property name="classes" value="c"/>
<property name="build.classpath" value="${classes}:${junit.home}"/>
Where c is a subdirectory containing your classes and junit.home is supposed
to be passed in from the external environment. If on a windows system you
set junit.home to d:\path (say its some project wide environment variable),
then the resulting value of build.classpath is
c:d:\path.
I would want that to be understood as a path consisting of c and d:\path.
Cheers
Conor
--
Conor MacNeill
[EMAIL PROTECTED]
Cortex eBusiness
http://www.cortexebusiness.com.au
> -----Original Message-----
> From: Tom Cook [mailto:[EMAIL PROTECTED]
> Sent: Monday, 3 July 2000 9:28
> To: [EMAIL PROTECTED]
> Subject: RE: Javadoc patch
>
>
> Conor MacNeill writes:
> [snip]
> > > (2) I feel returning the lookahead String in nextToken instead of
> > > scanning for a DOS path could be wrong in very strange cases (take
> > > c:d:\path for example, this would return c, d, \path). I could be
> > > wrong but maybe make it something like
>
> Is c:d:\path a valid path on DOSalike systems? I'd have thought
> c:;d:\path would be the way to express that; c:d:\path isn't really
> valid on anything, is it?
>
> Regards
> Tom
>
>
