On Fri, Nov 7, 2008 at 4:26 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Thread.sleep shouldn't be needed - usually you can set it to a time in the
> past, then read it back so that you know exactly the right value. Usually
> you need to use a low precision (whole seconds, at least) to get an accu
Thread.sleep shouldn't be needed - usually you can set it to a time in
the past, then read it back so that you know exactly the right value.
Usually you need to use a low precision (whole seconds, at least) to
get an accurate time. The less you can use it, the better.
I don't know of any li
On Sat, Oct 25, 2008 at 10:39 AM, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> DefaultWagonManagerTest has timestamp resolution issues as the test
> cases create new files which then have their timestamps checked to see
> if the downloaded file is newer than the one on disk.
>
> I know the eclipse:e
DefaultWagonManagerTest has timestamp resolution issues as the test
cases create new files which then have their timestamps checked to see
if the downloaded file is newer than the one on disk.
I know the eclipse:eclipse plugin had similar issues.
I've hacked around it by refactoring the newfile c
