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.
if server is not running
*** Issue 74307 has been marked as a duplicate of this issue. ***
The log file can be seen whether or not the server is running. This is a file on disk. Of course, it cannot be seen if there is no log file on disk
This is not about "View server log action" but about "View admin console" action => reopening
Sorry...I did not read enough... Now why I still think we should not fix this: sometimes, when things go wrong in the IDE or the plugin, and NB is not able to detect if the server is running or not (other bugs like profiler attachment), one way I found useful is to try the admin gui tool. So I would consider this as a value to try to open the admin gui url even when the server is not running (or if the IDE thinks it's not running yet, but it is in fact running). To much IDE control on things is sometimes bad, imo. Having the browser to tells the user the server is not running is better than an inactive menu item... Comments?
I agree with you, Ludo. Since the IDE can't be sure that it knows the exact status of the server, it's not a good idea to prevent user (who usually knows the status better) to do what he/she wants.
Ok, I don't have strong opinion on this. Sometimes it can be useful and sometimes it can be confusing. This bug/enhancement is more about consistency between server plugins - JBoss has similar action disabled if the server is not running. Mmocnak, can you follow up on this as a JBoss plugin representative, please?
As a plugin QE I'm constantly facing with this problem. Do we have any UI specs for them? I think they should be aligned.
*** This issue has been marked as a duplicate of 64483 ***
I am going to undup this... and reset issue 64483 to be server specific. Why not just start the server... and follow through on the action that the user is requesting... A parallel to this is the 'deploy' action on a project... if the server is not running, it gets started...
no bug should be assigned to issues. distributing the load.