Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
Consider turning off the console window when launching the FindBugs GUI. To implement this, change bin/findbugs.bat launcher line from this:
Hmm, sometimes FindBugs doesn't launch the UI - it just shows text in the console. Would this negatively impact users? Should we have findbugs.bat and findbugsw.bat?
The findbugs.bat by default uses java.exe, whereas it does have a "-gui" parameter that will select javaw.exe and a "-textui" parameter that will choose java.exe. I just think that since Microsoft Windows default behavior is not console but Window, so therefore javaw.exe might be a more natural default behavior. The user can still launch it as "findbugs.bat -textui" if they want the console to open as well, but in general it's not needed or desired since MS Windows by default has the windowing environment enabled. The only time I haven't seen the windowing environment enabled in MS Windows is when a MS Windows machine is booted into MS-DOS.
I think most Windows users that launch the findbugs GUI would create their own shortcut to the batch file and place that within the start menu, a toolbar, on desktop, etc.
I use a shortcut on quick launch, and that calls the findbugs.bat with the -gui parameter, which prevents the extra console window. Works for me.
Already done if findbugs is started with findbugs.bat -gui