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 Dev (Build 200801170000) VM: Java HotSpot(TM) Client VM, 10.0-b19 OS: Linux, 2.6.12-10-686, i386 User Comments:
Created attachment 55195 [details] stacktrace
I've tried to clone hg.nb.org/main and I've pushed "Create new IDE Project" button in the dialog asking what to do after clone itself.
I do not understand how to reproduce this from the comments. How do I access hg.nb.org/main?
I have cloned the project but have not been able to reproduce the problem reported. Can you give me exact instructions to reproduce the problem?
Uf sorry Padraig, I do not have any additional informations. If you look at http://statistics.netbeans.org/analytics/detail.do?id=20566 you'll find something important.
It looks like the only way that Projectutilities.newProjectWizard is called if a repository which does not contain any NetBeans project is cloned. However it is not clear how the parameter can not be a valid folder. I need instructions to reproduce this in order to solve it.
The problem is that you can get a null project if a project was cloned that isn't a NetBeans project, or you try and do a clone of a NetBeans project [local or remote] that does not have all the NetBeans project files, build.xml, project.properties ... committed. Proposed patch handles this error and warns the user.
Created attachment 55558 [details] Proposed patch
Created attachment 55764 [details] updated patch
changeset: 65157:ba0c4692b290 tag: tip user: padraigob@netbeans.org date: Wed Jan 30 13:44:46 2008 +0000 files: mercurial/src/org/netbeans/modules/mercurial/ui/clone/Bundle.properties mercurial/src/org/netbeans/modules/mercurial/ui/clone/CloneCompleted.java mercurial/src/org/netbeans/modules/mercurial/ui/clone/ProjectUtilities.java description: Issue 125466: fix exception when project is cloned.
I did not apply the patch correctly. Need to look at this again.
The fix for issue 126009 should also fix this issue. *** This issue has been marked as a duplicate of 126009 ***
v/c