I've been quiet for a while so I might as well jump in before going to bed.
I agree with Gregg that it would be better to honor equality of '/'
and '\'. This is a big pain, especially for new Jini users.
I don't like the Ant argument because I don't like Ant ;-) We use
Maven and I am not sure what the situation there is. It just seems
wrong to me to put this off on a build tool rather than fix it.
Sean
On Tue, May 20, 2008 at 8:14 PM, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> Mark Brouwer wrote:
>>
>> "With regard to RIVER-230 I'm wondering whether the request for
>> improvement is "a good thing", given the fact that ClassDep specifies
>> Platform specific classpaths and file paths. I don't think we should
>> take 'advantage' of the fact Java also accepts the wrong file separator
>> for the Windows platform. I believe that Ant can provide the proper
>> abstraction layer so you won't run into any problems as the build files
>> of the River project show, or that other Ant tasks on top of ClassDep
>> provide. Personally I would like to close RIVER-203 as "Won't fix", but
>> maybe I'm missing something, so please shoot if my reasoning is wrong."
>
> This is what I was disagreeing with. The Java platform already honors the
> mixed usage. I assert that this is a good thing because the contents of
> executable Jar files can contain file paths that need to be acceptable on
> all Java VMs.
>
> This expectation, in my opinion, is not unrealistic and thus I am bringing
> my view here. I appreciate that in the case of Ant, there is ${/}. But,
> there are other ways to run ClassDep and I think that supporting / and \ as
> equivalent is something that makes sense because the Java platform already
> does.
>
> Gregg Wonderly
>
