Date: Fri, 18 Jan 2019 12:48:25 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 235018] java/openjdk8: adding millisecond resolution to get/setLastModified breaks many apps Message-ID: <bug-235018-8522-FaooCqihBw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235018-8522@https.bugs.freebsd.org/bugzilla/> References: <bug-235018-8522@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235018 --- Comment #7 from Alex Dupre <ale@FreeBSD.org> --- I'm sorry about your breakage, but you are confusing the java spec with a specific implementation on a specific OS. Both Java 8 and Java 11 have the = same spec in relation to the getLastModifiedTime resolution, and there are alrea= dy implementations on different OSes / filesystems / JREs that returns the correct/documented resolution, so every application that fails because it blindly ignores the milliseconds is simply flawed, included tomcat if it compares a millisecond value with a second value multiplied by 1000 instead= of the opposite. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235018-8522-FaooCqihBw>