This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 125904

Summary: local history not available
Product: versioncontrol Reporter: mikeburke <mikeburke>
Component: LocalhistoryAssignee: issues@versioncontrol <issues>
Status: RESOLVED DUPLICATE    
Severity: blocker    
Priority: P1    
Version: 6.x   
Hardware: PC   
OS: Windows Vista   
Issue Type: DEFECT Exception Reporter:
Attachments: screnshot
Messages log from issue occurrance.

Description mikeburke 2008-01-24 10:17:21 UTC
When I attempt to view local history (right click on file in projects view, select 'local history') I see nothing but 
a two-tone window with shades of blue, with the bottom half simply saying ("right click").

I have made and saved changes to the file, which is part of the project, and 'keep local history' in options is set to 
7 days.

Have attached a screenshot.
Comment 1 mikeburke 2008-01-24 10:20:16 UTC
Created attachment 55481 [details]
screnshot
Comment 2 mikeburke 2008-01-24 10:21:46 UTC
Help->About as follows:
Product Version: NetBeans IDE 6.0 (Build 200711261600)
Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
System: Windows Vista version 6.0 running on x86; Cp1252; en_AU (nb)
Userdir: C:\Users\Mike\.netbeans\6.0

Local History plugin is v1.1.2
Comment 3 Tomas Stupka 2008-01-24 18:35:37 UTC
is this reproducible for you? do you get this behavior every time you open the local history for whatever file.

could you please attach your messages.log file from the nb session when this happened?

thanks
Comment 4 mikeburke 2008-01-27 03:42:56 UTC
Created attachment 55615 [details]
Messages log from issue occurrance.
Comment 5 mikeburke 2008-01-27 03:45:05 UTC
Yes, this is reproducible, regardless of file or project in use.

I've attached a messages log, showing an NPE in sun.swing.table.DefaultTableCellHeaderRenderer.getColumnSortOrder():104
Comment 6 Tomas Stupka 2008-01-28 11:19:17 UTC
this seems to be already fixed. see issue #119569 for more information.

possible workarounds are
- downgrade your JDK to JDK6u3 version
- change L&F to windows classic

*** This issue has been marked as a duplicate of 119569 ***