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.

Bug 110990 - Verifier display settings does not persist
Summary: Verifier display settings does not persist
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
: 67944 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-07-25 17:48 UTC by Sherold Dev
Modified: 2009-12-21 06:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sherold Dev 2007-07-25 17:48:59 UTC
Steps to reproduce

1. Create an EAR application
2. Run the Verify action
3. Switch the display settings to "Failures only"
4. Run the Verify action again

Display method will be switched back to: "All Results". Having to switch the display setting every time I run the Verify
action becomes quite bothering after some time.
Comment 1 Nitya Doraisamy 2007-10-12 19:29:37 UTC
Verifier task spawns a new verifier window every time the action is called and does not reuse the previous one and hence
the new window has all the default settings. Need to fix the action so as to reuse existing window and persist settings,
(atleast on a project basis)
Comment 2 Nitya Doraisamy 2007-10-12 19:32:23 UTC
*** Issue 67944 has been marked as a duplicate of this issue. ***
Comment 3 Vince Kraemer 2008-10-18 03:33:13 UTC
does v3 have a verifier...

if not, lower to p4

please be prepared to discuss this issue on 2008/10/22
Comment 4 Nitya Doraisamy 2008-12-09 17:41:27 UTC
GlassFish v3 prelude does not have verifier available, so this is a v2 fix. Downgrading to P4, add to task list for 7.0
Comment 5 Quality Engineering 2009-12-21 06:05:35 UTC
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team