On 07/23/2014 05:28 PM, Zhong Yu wrote:
As an example, on this page
http://docs.oracle.com/javase/8/docs/api/java/lang/Class.html
the 'FRAMES' link is
http://docs.oracle.com/javase/8/docs/api/index.html?java/lang/Class.html
i.e. the `targetPage` is embedded as a query.
This is a proble
As an example, on this page
http://docs.oracle.com/javase/8/docs/api/java/lang/Class.html
the 'FRAMES' link is
http://docs.oracle.com/javase/8/docs/api/index.html?java/lang/Class.html
i.e. the `targetPage` is embedded as a query.
This is a problem for web crawlers, to them
http://docs.
At Google we also strive for repeatable builds. We find timestamps
embedded in jar files to be the biggest problem.
Timestamps are useful for users checking up-to-dateness via the "Show
Source" action in a web browser.
Making the choice of timestamp explicit in a javadoc invocation seems like
a
From: Benedikt Morbach
having those timestamps in there generally isn't that useful and causes
unnecessary differences between builds that you have to cope with, e.g.
if you want to ensure that a binary you got matches the source code.
Some Linux distributions are working on making builds reprod
