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 216374 - Subversion preparing commit shows no files
Summary: Subversion preparing commit shows no files
Status: RESOLVED DUPLICATE of bug 212318
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Subversion (show other bugs)
Version: 7.2
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Ondrej Vrabec
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-03 14:55 UTC by jmsoft
Modified: 2012-08-06 08:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
messages.log aquired via e-mail (163.40 KB, text/plain)
2012-08-06 08:49 UTC, Ondrej Vrabec 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jmsoft 2012-08-03 14:55:54 UTC 
Hi,

Before I switched from Netbeans 7.1.2 to 7.2 subversion update and commit worked ok.
After the switch when I select Subversion commit the list of files to be committed remains empty even after update or update with dependencies.

Regards
Comment 1 Ondrej Vrabec 2012-08-03 17:52:05 UTC 
Hi,
attach the messages.log file (http://wiki.netbeans.org/FaqLogMessagesFile) after you open the commit dialog.
What files are listed in the Versioning view after you run Subversion -> Show changes ?
Comment 2 Ondrej Vrabec 2012-08-06 08:49:20 UTC 
Created attachment 122773 [details]
messages.log aquired via e-mail
Comment 3 Ondrej Vrabec 2012-08-06 08:50:25 UTC 
from the messages.log:
> SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor org.netbeans.modules.subversion.ui.status.VersioningPanel$RefreshViewTask
> java.lang.NullPointerException
> 	at org.tmatesoft.svn.core.internal.util.SVNPathUtil.getRelativePath(SVNPathUtil.java:465)
> 	at org.tmatesoft.svn.core.javahl17.SVNClientImpl.getInfo(SVNClientImpl.java:2185)
> ...
dup of #212318

*** This bug has been marked as a duplicate of bug 212318 ***