How will the webrev script in existing repos be updated?

[Stuart Marks]

On 1/7/14 10:58 AM, Mike Duigou wrote:
> On Jan 7 2014, at 10:50 , Stuart Marks <stuart.marks at oracle.com> wrote:
>> I'd like to have one copy in CODETOOLS that everybody can use.
>
> Yep. Getting it to people is going to be the issue. I have heard grumblings about the annoyance of installing/updating jcheck locally. I suspect that with moving to CODETOOLS we are going to see more incidents of people using stale webrev again. It had been nice for a while in 8 that people were moving towards using the bundled up-to-date webrev rather than some hoary old version. Perhaps this might be a case where we can legitimately use mecurial sub-projects?

Fortunately webrev.ksh is just a single file, and it's easy enough to formulate 
a URL directly into the code-tools/webrev repo to get this one file:

http://hg.openjdk.java.net/code-tools/webrev/raw-file/tip/webrev.ksh

This at least avoids the rigamarole of having to clone yet another repo and keep 
it updated, just to get the latest webrev. I think this URL is safe to put into 
README files and wiki pages and such.

s'marks