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.
Build: NetBeans IDE 6.0 RC1 (Build 200711081200) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Linux, 2.6.22-14-386, i386 User Comments:
Created attachment 53255 [details] stacktrace
could you please attach your messages.log file? thanks
Created attachment 53256 [details] Messages logs
few more questions: - what is your svn client version? - how was the working copy created? checked out by the nb svn module, or by some another client? - do you always get this problem, with every svn action, or only that one time you invoked the update thanks
taken from the reporters mail: first time svn client 1.4 on kubuntu gutsy gibbons (not on the computer now) first time i get it, maybe because I ran the update from netbeans twice in a row without waiting for the firs to terminate
so, do i understand right - the update usually works for you?
how did you invoke the update - from the toolbar in the subversion window, or from the menu (context or main)?
*** Issue 123676 has been marked as a duplicate of this issue. ***
*** Issue 125834 has been marked as a duplicate of this issue. ***
This issue has already 5 duplicates
This issue has already 10 duplicates
StackTrace: =========== java.lang.NullPointerException at org.netbeans.modules.subversion.Subversion.getClient(Subversion.java:222) at org.netbeans.modules.subversion.Subversion.getClient(Subversion.java:259) at org.netbeans.modules.subversion.ui.update.UpdateAction.update(UpdateAction.java:148) at org.netbeans.modules.subversion.ui.update.UpdateAction.access$000(UpdateAction.java:74) at org.netbeans.modules.subversion.ui.update.UpdateAction$1.perform(UpdateAction.java:109)
Build: NetBeans IDE 6.0.1 (Build 200801291616) VM: Java HotSpot(TM) Client VM, 1.5.0_13-119 OS: Mac OS X, 10.5.2, i386 User Comments:
Created attachment 59753 [details] stacktrace
wasn't reported with 6.1 anymore (since build 071129) - seems to be fixed
This bug it's still present in NetBeans 6.1
could you please attach your messages.log
Build: NetBeans IDE 6.1 (Build 200804211638) VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_05-b13 OS: Windows XP, 5.1, x86 User Comments: I tried to refresh in the panel 'subversion'.
Created attachment 61285 [details] stacktrace
Created attachment 61424 [details] stacktrace
*** Issue 134299 has been marked as a duplicate of this issue. ***
*** Issue 138337 has been marked as a duplicate of this issue. ***
*** Issue 139171 has been marked as a duplicate of this issue. ***
Build: NetBeans IDE Dev (Build 200807100006) VM: Java HotSpot(TM) Server VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_04-b12 OS: Windows XP, 5.1, x86 User Comments: refreshing on "Subversion" Tab
Created attachment 64307 [details] stacktrace
Build: NetBeans IDE Dev (Build 200807010102) VM: Java HotSpot(TM) Client VM, 11.0-b13, Java(TM) SE Runtime Environment, 1.6.0_10-rc-b26 OS: Linux, 2.6.24-19-generic, i386 User Comments: SVN Check out, uninstall svn, go to "project properties", Java Sources
Created attachment 64809 [details] stacktrace
fixed 7ba3eeb1bb22
i will miss this one ...
Marked as fixed, yet nightly build of NB 6.5 dev 200808300201 tells me it had this one.
could you attach your file?
lewisbloch: i guess, you are referring to issue #145080 this is issue is a mess - too many stacktraces, and unfortunately covering 2 different NPEs as i just realized. there are more getClient methods in that class, and the reported exceptions were thrown for different reasons at different places. One of them is definitely fixed. Lets keep track of the other one in 145080.
This issue still exists, at least as of NB 6.5 dev 200808300201.
Reviewed comments. I thought the log was uploaded automatically by the NetBeans bug-reporting mechanism. Unfortunately I no longer have the log. It was the NB bug-reporting system that led to this issue, of which it seems to think the real issue a duplicate. Transferring attention now to #145080.
> I thought the log was uploaded automatically by the NetBeans bug-reporting mechanism. some log information get uploaded indeed. unfortunately, not the whole messages.log file and the particular info i was looking for wasn't included.
Reopening - reproduced in NetBeans IDE Dev (Build 200810080201) http://statistics.netbeans.org/exceptions/detail.do?id=124999
Reopening - reproduced in NetBeans IDE Dev (Build 200810080201) http://statistics.netbeans.org/exceptions/detail.do?id=125001
*** Issue 153270 has been marked as a duplicate of this issue. ***
*** Issue 152511 has been marked as a duplicate of this issue. ***
is there anybody able to reproduce and provide his messages.log? thanks
*** Issue 116817 has been marked as a duplicate of this issue. ***
*** Issue 155615 has been marked as a duplicate of this issue. ***
Sorry for my English... But may be this explanation can help. At first and second IDE start, context menu not have Subversion item and main menu Versioning->Subverion->... throw exception. If IDE restarted 3 times all works properly.
was able to reproduce: 1.) two projects -> one versioned in svn and the another unversioned 2.) select 1 file from the versioned project and one from the unversioned 3.) choose show changes from context menu or main menu
fixed VCS context so that returns only versioned files. changeset : 114307:7f41de0a3346 author : Tomas Stupka <tstupka@netbeans.org> date : Mon Jan 19 14:59:39 CET 2009 summary : #122411 - Subversion.getClient throws NPE
Integrated into 'main-golden', will be available in build *200901200201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/7f41de0a3346 User: Tomas Stupka <tstupka@netbeans.org> Log: #122411 - Subversion.getClient throws NPE VCSContext shouldn't return versioned and unversioned rootFiles
*** Issue 156418 has been marked as a duplicate of this issue. ***
this looks fixed in trunk - btw: 270 duplicates (some also for 6.5.1)
hopefully fixed in trunk
*** Issue 161669 has been marked as a duplicate of this issue. ***
I believe that this issue is fixed. But I have never seen this problem and have no clue how to verify this. Could please someone who is fighting this issue try to verify it in latest build from the trunk? Thanks.
back-port to 6.5 fixed as release65_fixes #66d01a9c4d90
Verified. The issue is not reproducible in 6.5.1 + patch4.