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 # : 201109070600 ] [ JDK VERSION : 1.7 ] If given cachedir does not exist, netbeans stops loading - without an info. it would be better to inform the user about the problem
(In reply to comment #0) > If given cachedir does not exist, netbeans stops loading - without an info. Seems to work fine for me on Linux. Are there are particular steps to reproduce? Can you attach $userdir/var/log/messages.log if it gets that far? Perhaps the failure is in the Windows launcher before the Java process is even started?
(In reply to comment #0) > [ BUILD # : 201109070600 ] > [ JDK VERSION : 1.7 ] > > If given cachedir does not exist, netbeans stops loading - without an info. Do you mean, it physically doesn't exist, e.g. not connected/mounted USB-drive?
I was only able to reproduce a problem with --cachedir if the path I provided was an unreachable path on my machine. E.g. "--cachedir i:\tmp\cache" where the disk i: does not exist on my windows box. If the path did not exist but the folder could be created, NetBeans started normally, created the folder and started storing the cache data there. In the case of unreachable path the following log messages were written to messages.log: WARNING [org.openide.modules.Places]: could not create I:\tmp\cache We could probably raise a dialog box and tell the user that NetBeans cannot reach the path. Decreasing to P3 and reassigning. The code in org.openide.modules.Places should show the warning.
Created attachment 110703 [details] var/log/messages when cachedir not exists
sorry for late reply. yes i can confirm: if just the path did not exists, netbeans created it. but if the drive did not exists, netbeans just dies. I discovered this because the ramdisc for the the cache did not work :) in the messages log (attached) the error is written correctly. would be better to inform the user :)
org.openide.modules.Places cannot and should not show a warning dialog. It is possible there is some place in core where this could be done, but it seems a low priority; the Windows launcher itself will in a future release set --cachedir and might do some checks before starting the Java process.
Assigned to new owner.