Hi Burt, This is known issues and current limitation in Jupiter which can not handle the review links after some refactoring (especially changing the LOC).
> What was helpful was that some authors would copy/paste a small fragment of > the code they were referring to. This would help some for the author in rework phase to match the review comment with the actual codes after some refactoring :-) However, instead of forcing reviewers to copy (cite) some chuck of actual source codes in the review editor, I am wondering if Jupiter can stick to a revision version of cvs and review and rework to the version. In this case, you might refactoring the reviewed code, comparing with the revision source code at the time reviewers did. Cheers, Takuya On Tue, 19 Oct 2004 01:05:44 -1000 Burt Leung <[EMAIL PROTECTED]> wrote: > Hello Everyone, > > > > After doing a lot of refactoring today I discovered that a lot of the links > in the review comments were broken. > > > > What was helpful was that some authors would copy/paste a small fragment of > the code they were referring to. > > > > I suggest that this be done for all code reviews. > > > > It makes it easier to track done the piece of code that a review comment is > referring to if the link is broken. > > > > In any case, thanks for all your feedback in your review comments. > > > > Burt > > > > > > > ================================ Takuya Yamashita E-mail: [EMAIL PROTECTED] ================================
