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 # : beta ] [ JDK VERSION : <1.6.20 ] In netbeans.conf I have set: netbeans_default_options="-J-client -J-Xss2m -J-Xms32m -J-XX:PermSize=32m -J-Dnetbeans.logger.console=true -J-ea -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true -J-Dsun.zip.disableMemoryMapping=true -J-Dnetbeans.winsys.statusLine.in.menuBar=true --cachedir \"${HOME}\Lokale Einstellungen\Anwendungsdaten\NetBeans\7.1beta\cache\"" When I launch NB IDE, the splash screen appears, and after 10..20 seconds it disappears again without any further action or notice. When I set: --cachedir \"C:\Dokumente und Einstellungen\xxx\Lokale Einstellungen\Anwendungsdaten\NetBeans\7.1beta\cache\" all works fine, but this setting is not multi-user capable.
Assigned to new owner.
Hello, on Windows ${HOME} will never work. ${HOME} is not standard environment variable like on Linux. So you bug is irrelevant. Closing Thank you for your interest in NetBeans.
1. In netbeans.conf I read: "${HOME} will be replaced by JVM user.home system property" ... so we don't speak about environment variable here. 2. Anyway, if I use ${HOME} or Windows standard %USERPROFILE% variable, IDE launcher should work or return a message, but not die silently.
The problem of the current behaviour is, that the user is still waiting some time if anything happens later, especially on older slower computers. Additionally there remains a doubt, if some hidden processing is still running, so user has to inconveniently check this e.g. by task-manager. This doubt could be solved by prompting the user with something like: "NetBeans Launcher has aborted because of xyz". Regardless of the here given cause, it seems not rare, that user is checking out new settings in netbeans.conf in a loop. In such case it's very boring to always check, if netbeans.exe is still running or not.
(In reply to comment #3) > 1. In netbeans.conf I read: > "${HOME} will be replaced by JVM user.home system property" > ... so we don't speak about environment variable here. You are right this is mentioned in netbeans.conf, but it's only related to netbeans_default_userdir and netbeans_default_cachedir properties. If you use it in netbeans_default_options property it won't work. But your report help us to find bug in using netbeans_default_cachedir property (/core-main/rev/b1e2bf17e9af) so in next dev build you can setup netbeans_default_cachedir with ${HOME} instead of using --cachedir switch in netbeans_default_options. I hope this would fix your problems.
(In reply to comment #5) > (In reply to comment #3) > > 1. In netbeans.conf I read: > > "${HOME} will be replaced by JVM user.home system property" > > ... so we don't speak about environment variable here. > You are right this is mentioned in netbeans.conf, but it's only related to > netbeans_default_userdir and netbeans_default_cachedir properties. If you use > it in netbeans_default_options property it won't work. This is not obvious to the reader, so user as me wastes his time checkout correct usage. I think, there should be an additional hint, where it is valid, and where not. > But your report help us to find bug in using netbeans_default_cachedir property > (/core-main/rev/b1e2bf17e9af) so in next dev build you can setup > netbeans_default_cachedir with ${HOME} instead of using --cachedir switch in > netbeans_default_options. > > I hope this would fix your problems. Great!
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #3) > > > 1. In netbeans.conf I read: > > > "${HOME} will be replaced by JVM user.home system property" > > > ... so we don't speak about environment variable here. > > You are right this is mentioned in netbeans.conf, but it's only related to > > netbeans_default_userdir and netbeans_default_cachedir properties. If you use > > it in netbeans_default_options property it won't work. > This is not obvious to the reader, so user as me wastes his time checkout > correct usage. I think, there should be an additional hint, where it is valid, > and where not. Definitely yes, we will clarify it.
IDE launch still aborts without notice on wrong/invalid settings in netbeans.conf. --> So this bug is not fixed! (maybe won't fix) IMHO: IDE launcher should work or return a message, but not die silently.
This is still an issue with a Platform app built on NetBeans IDE 7.2 Beta (Build 201205031832), "netbeans_default_cachedir" (and "default_cachedir" which I've also tried) doesn't set the cache directory, so when installed on a Windows machine it exits (because the cache is "." and is read-only).
netbeans.conf has been reviewed and the text about ${HOME} has been clarified in issue 210593 - http://hg.netbeans.org/core-main/rev/5c0d0c7c7709