Currently, "fingerprint" and "module-info-path" appear to have to be used
together, but they should be able to be enabled separately.
When module-info-path is not specified, then the module info is prepended to
the root module.
Later, if fingerprint is calculated, then they are based on the module contents.
Once that happens, the module info in the root module is invalid because that
info does contains the unfingerprinted URLs rather than the fingerprinted ones.
In practice, they are often used together, which is probably why this bug has
not been reported sooner.
Original issue reported on code.google.com by bolinf...@gmail.com on 28 Oct 2011 at 4:03
Original issue reported on code.google.com by
bolinf...@gmail.comon 28 Oct 2011 at 4:03