ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Cooper" <martin.coo...@tumbleweed.com>
Subject Re: Conditional chmod
Date Thu, 02 Nov 2000 08:44:13 GMT
You ask why it isn't ignored on Windows? Actually, I've been wondering why
it *is* ignored.

Certainly, Windows doesn't support the same file modes that some other
systems do, but how do I set or clear the read-only attribute on files under
Windows? How about the archive attribute? Is there a Windows equivalent to
the Unix chmod within Ant that I'm not aware of?

Of course, calling the task 'chmod' in the first place does indicate a
strong bias towards a certain OS on the part of the Ant developers, which
seems more than a little inappropriate in a tool which purports to be OS
independent...

--
Martin Cooper
Tumbleweed Communications

----- Original Message -----
From: "Holger Rauch" <Holger.Rauch@heitec.de>
To: "Nico Seessle" <Nico.Seessle@epost.de>
Cc: <ant-user@jakarta.apache.org>
Sent: Thursday, November 02, 2000 12:28 AM
Subject: Re: Conditional chmod


> Hi!
>
> On Sun, 29 Oct 2000, Nico Seessle wrote:
>
> > It should normally do exactly that, ignore it on Windows. This depends
on
> > several properties your Java VM provides. Can you run ant -debug and
post
> > the values for path.separator and os.name?
>
> My colleague, who is working with Windows 2000, has run "ant
> -verbose..." and received the following for path.separator and os.name
>
> path.separator: ;
> os.name: Windows 2000
>
> Anyway, I don't have the faintest idea why a chmed is not ignored on Win*.
>
> Thanks for any help!
>
> Regards,
>
> Holger
>



Mime
View raw message