> the javadoc tool merely checks the existence of the remote
> documentation to add href links in the generated files.
Mm. This also happens with Python's "Sphinx" documentation framework.
> This is optional and doesn't break the build if it doesn't work.
Builds may not even _attempt_ access IMHO - whether it FTBFS or not is
irrelevant from this point of view.
This is for many reasons, including leaking the privacy of anyone
rebuilding our packages and, as you mention, reproducibility.
> I think this is a rather minor policy violation
I'm afraid not. Policy actually explicitly agrees with my own opinion
here for once (am not wielding it as a stick!).
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
debian-j...@lists.debian.org for discussions and questions.
