You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Peter Donald <do...@mad.scientist.com> on 2000/09/16 04:01:15 UTC

Re: Patch to Javac to check if .class exists before warning that .java is modified in the future

At 08:31  15/9/00 -0400, you wrote:
>The reason I'm making this patch is because of what I think is a problem
>with the Win98 filesystem in that I do a copydir task of my source files to
>the build area and then compile from my build area.  There is no reason I
>should be getting the warning in the first place, but I think there is a
>resolution in the timestamp of a file that may force it into the future.

Hmm a better method would be to fix copy method. We could do this by
copying into a temporary file and then file.rename( destination ) to move
it to final destinaiton. This would fix all problems even on crappy OSes :P


Cheers,

Pete

*------------------------------------------------------*
| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power."          |
|       -Abraham Lincoln                               |
*------------------------------------------------------*

RE: Patch to Javac to check if .class exists before warning that .java is modified in the future

Posted by Scotte Zinn <sz...@patronix.com>.
Just tried fixing the copyFile method in Project.java and the warning still
shows up.

-- Scotte

-----Original Message-----
From: Peter Donald [mailto:donaldp@mad.scientist.com]
Sent: Friday, September 15, 2000 10:01 PM
To: ant-dev@jakarta.apache.org
Subject: Re: Patch to Javac to check if .class exists before warning
that .java is modified in the future


At 08:31  15/9/00 -0400, you wrote:
>The reason I'm making this patch is because of what I think is a problem
>with the Win98 filesystem in that I do a copydir task of my source files to
>the build area and then compile from my build area.  There is no reason I
>should be getting the warning in the first place, but I think there is a
>resolution in the timestamp of a file that may force it into the future.

Hmm a better method would be to fix copy method. We could do this by
copying into a temporary file and then file.rename( destination ) to move
it to final destinaiton. This would fix all problems even on crappy OSes :P


Cheers,

Pete

*------------------------------------------------------*
| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power."          |
|       -Abraham Lincoln                               |
*------------------------------------------------------*