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.
Created attachment 104901 [details] screenshot of the installer's error message I ran the installer of NetBeans 6.9.1 for Windows. I customized the intallation configuration by unchecking options Java ME, Groovy and Glassfish. The installation seems to have been successful, just that the installer displayed an error message at the end (see the attachment). I have had Git installed before I started the NetBeans installer but I do not see why the installer should be affected by this fact. I have administration rights on the PC and I installed NetBeans to the default location (C:\Program Files\NetBeans 6.9.1). -- NetBeans 6.9.1 (Java pack), installed without Java ME, Groovy and Glassfish JDK 6u23 (Windows, 32-bit) Windows XP Professional, 32-bit Intel quad-core PC
ugh, i have no idea why the installer is interested in git. Please, Marian, could you start the installer with '--verbose > out.txt', go through the installation process again and attach the output (out.txt)?
Created attachment 104918 [details] verbose output of the installer
Created attachment 104919 [details] list of executables on PATH installed by the Git installer
My guess is that the NetBeans installer tried to execute some utility whose name matched some Git-specific utility on PATH. Attached is the list of executables installed and added to PATH by the Git installer.
Please run netbeans-6.9.1-ml-windows.exe --extract then "C:\Program Files\Java\jdk1.6.0_23\bin\java.exe" -jar bundle.jar > out.txt 2>&1 And attach resulting out.txt. That would clarify at which point that error message is produced.
Created attachment 104946 [details] output of "java.exe -jar bundle.jar" I did not see the message this time (with installer launched with "java -jar bundle.jar"). That seemed interesting to me so I uninstalled NetBeans again and installed it the common way - and this time I did see the message. I forgot to say that the message is always displayed at the end of uninstallation process, too.
*** Bug 197820 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > Created an attachment (id=104946) [details] > output of "java.exe -jar bundle.jar" > > I did not see the message this time (with installer launched with "java -jar > bundle.jar"). The message is yet logged: > [2011-01-13 07:31:08.993]: ... creating JFileChooser object to check possible issues with UI > fatal: Not a git repository (or any of the parent directories): .git > [2011-01-13 07:31:09.196]: ... getting default Toolkit to check possible issues with UI I tried to reproduce (installed Git, added Git\cmd and Git\bin onto PATH) but was unsuccessful. Marian, can you run the installer several times in a row (using java.exe -jar bundle.jar) and check if the message is still logged on the same place (after 'creating JFileChooser object to check possible issues with UI')? Since the message is logged during the installer startup, you don't need to go through the whole installation process, just wait for the installer to initialize and check the output. Because looking at the relevant code, there's no external process called (http://hg.netbeans.org/core-main/file/tip/nbi/engine/src/org/netbeans/installer/utils/UiUtils.java#l274).
Hello. Now I've installed NetBeans 7.0 (jdk-6u26-nb-7_0-windows-ml.exe) and got the same error message. Git-1.7.4-preview20110204 is installed on my computer with "Git Cheetah" Explorer extension. When I disabled Git Cheetah using ShellExtView (http://www.nirsoft.net/utils/shexview.html) and repeated NetBeans installation, "not a git repository" error message gone. BTW, same error appears in Far Manager, version 2.0 (build 1807) x86 when I trying to open files or folders context menu using EMenu plugin. Error message is appeared not in command prompt, but in background of console window. Therefore this is Git Cheetah problem, I think.
Created attachment 108843 [details] Screenshot of Far Manager with same error message
I think I have TortoiseGit installed at work (where I observed the bug). Uninstalling it might help. But I do not want to risk breaking my development environment by reinstalling Git and NetBeans so I will not try it.
Created attachment 109135 [details] Example case of JFileChooser and Git interaction Hi, I'm new here, so I hope I'm doing this correctly. I found this bug report while searching for a solution to this same problem, but that was occurring in one of my own applications. I isolated to problem to a call to the JFileChooser constructor. I have attached a simple test case which illustrates the problem. I included a non-GIT directory (c:\) and a git directory ('c:\gittest'). The former reports the fatal not a git repository error, while the latter does not. output: c:\workspace> java GitAndJFileChooser Before JFileChooser constructor fatal: Not a git repository (or any of the parent directories): .git Before showOpenDialog After showOpentDialog Now trying on a Git repository directory Before JFileChooser constructor [git directory] Before showOpenDialog [git directory] After showOpentDialog [git directory] My JRE version is: java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing) git was installed from Git-1.7.4-preview20110204.exe The only git directory in my path is c:\program files\git\cmd, and the git command is git.cmd from that directory. I hope this is helpful.
I am getting this with same specs and Git installed but with NetBeans 7.1 beta.
The idea is any *stderr* caught during installer run is shown after installer is fininished. That usually helps to catch mysterious issues and show them to user, mostly in case when main installer window was not shown at all. So, at least, we show some this message and user got a feeling that something got bad rather than not to show anything. But some programs (and even java itself) dump unnecessary staff to stderr see e.g. Bug 105165. Sometimes it is just diagnostic message, sometimes it is a real error and thus should be reported somehow. Let me propose a patch to fix this issue. In 2 words, we would filter known diagnostic messages (as of now - this git one and another from java launcher) and show error message with stderr after installer is finished with non-zero exit code (i.e. something went wrong during installation).
Created attachment 113980 [details] Patch for nbi/engine/native/launcher/windows/src/Launcher.c
Created attachment 113981 [details] Rebuilt nbi/engine/native/launcher/windows/dist/nlw.exe with patch to Launcher.c applied NB: nlw.exe should be rebuilt using Microsoft Platform SDK tooling and not cygwin one. http://wiki.netbeans.org/NBIBuildRequiredSoftware E.g. I have always used the following command on my system with Microsoft tools installed: "C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin\nmake.exe" /f Makefile-vc-wo-crt
(In reply to comment #16) > Created attachment 113981 [details] > Rebuilt nbi/engine/native/launcher/windows/dist/nlw.exe with patch to > Launcher.c applied > > NB: nlw.exe should be rebuilt using Microsoft Platform SDK tooling and not > cygwin one. > http://wiki.netbeans.org/NBIBuildRequiredSoftware > > E.g. I have always used the following command on my system with Microsoft tools > installed: > "C:\Program Files\Microsoft Platform SDK for Windows Server 2003 > R2\Bin\nmake.exe" /f Makefile-vc-wo-crt Thank you very much. I have fixed this exactly as you described. Fixed in changeset: core-main/rev/fd9a226b315e
I hope you've rebuild nlw.exe by yourself :) The one that I've attached to this issue was created a few months ago, and after that I already have changed. See history: http://hg.netbeans.org/core-main/log/tip/nbi/engine/native/launcher/windows/dist/nlw.exe If haven't do that, and don't have environment set up for that (and Jirka does not have it as well) as in Commnent 16, please let me know - I can re-build nlw.exe again with the fresh sources. http://netbeans.org/bugzilla/show_bug.cgi?id=194242#c16
Yes, I have built it by myself using MS Visual Studio 2010. I was fighting a little bit with it, but I hope the final nlw.exe is fine. I also made some test on Win7 and WinXP and it seem's everything is ok... Thanks