ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Cooper" <>
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

Martin Cooper
Tumbleweed Communications

----- Original Message -----
From: "Holger Rauch" <>
To: "Nico Seessle" <>
Cc: <>
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
> > several properties your Java VM provides. Can you run ant -debug and
> > the values for path.separator and
> My colleague, who is working with Windows 2000, has run "ant
> -verbose..." and received the following for path.separator and
> path.separator: ;
> Windows 2000
> Anyway, I don't have the faintest idea why a chmed is not ignored on Win*.
> Thanks for any help!
> Regards,
> Holger

View raw message