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.
[ JDK VERSION : 1.6.0 ] NullPointerException when try to diff remote changes Steps 1 Create project and add it to SVN repo 2 Change it locally (make a local change) 3 invoke show changes 4.try to diff change file
I actually tried with 3 different projects and none of them threw NPE. Does it show for a specific filetype?? Did u add it to your SVN repo?? I have tried starting a new project to a repository as well as existing project and still couldn't get the exception... Does it work fine with a pre-existing project in the repo and checking the diff??
what is your version my one is deadlock Build 20080715105254 on XP
Im using the Build 200807101204 on Windows Vista (JDK 1.6.0_u10) and cannot generate this error.
It start happen from yesterday try this http://deadlock.netbeans.org/hudson/job/trunk/lastSuccessfulBuild/artifact/nbbuild/dist/zip/ build
There is no stack trace here in this report but I assume this is a dup, reopen otherwise. *** This issue has been marked as a duplicate of 139768 ***
java.lang.NullPointerException at org.netbeans.modules.diff.builtin.visualizer.editable.EditableDiffView$RefreshDiffTask.computeDiff(EditableDiffView.java:980) at org.netbeans.modules.diff.builtin.visualizer.editable.EditableDiffView$RefreshDiffTask.run(EditableDiffView.java:948) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) at org.netbeans.modules.diff.builtin.visualizer.editable.EditableDiffView.<init>(EditableDiffView.java:267) at org.netbeans.modules.diff.builtin.DefaultDiffControllerProvider.createDiffController(DefaultDiffControllerProvider.java:58) at org.netbeans.api.diff.DiffController.create(DiffController.java:90) at org.netbeans.modules.subversion.ui.diff.MultiDiffPanel$DiffPrepareTask.run(MultiDiffPanel.java:672) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)
Yes, the stack trace confirms this is a dup. *** This issue has been marked as a duplicate of 139768 ***
I see is this fix on deadlock ?