You need to log in before you can comment on or make changes to this bug.
the mercurial versioning view is set to TopComponent.PERSISTENCE_ALWAYS in HgVersioningTopComponent but it does not persist its actual state at all. The resulting effect is that the view gets opened after a netbeans restart without having a context set - it's empty even if there were modifications before restart and a refresh from the toolbar doesn't help either. note, that there is a problem in the versioning api - VCSContext isn't serializable - see issue #129268. i suggest you wait until issue 129268 gets fixed so you don't have to hack your way around with a parallel context implementation like svn, clearcase & co did.
Should we change this to TopComponent.PERSISTENCE_NEVER, until this is fixed or should we just leave as is?
if you decide to stay with vcscontext and wait until 129268 gets fixed (not in in 6.1) then setting PERSISTENCE_NEVER would make sense as the way it works now is a bit strange.
Change to TopComponent.PERSISTENCE_NEVER so behavior is consistent. Will reset to TopComponent.PERSISTENCE_ALWAYS when 129268 is available. changeset: 72394:14405d40204e tag: tip user: jrice@netbeans.org date: Mon Mar 10 16:35:47 2008 +0000 summary: #129276: mercurial versioning view doesn't persist it's state - needs #129268 to be fixed, for now disable Status View persistence
Changing to enhancement, need VSContext persistence support
*** This issue has been marked as a duplicate of 143300 ***
