Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 168874

Summary: [Vista] Windows informational dialog when generating JScrib test reports.
Product: z_Archived Reporter: Paul Slauenwhite <paulslau>
Component: TPTPAssignee: Paul Slauenwhite <paulslau>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P2 CC: paulslau
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard: housecleaned460
Attachments:
Description Flags
JScrib_Report_Error.jpg none

Description Paul Slauenwhite CLA 2006-12-21 12:52:57 EST
[Vista] Windows informational dialog when generating JScrib test reports.

The enclosed Windows informational dialog opens when the user first generates a JScrib test report informing the user that the OS' color schme is being temporarily changed to Windows Vista Basic.

At the least, we need to document this in the 4.2.2 readme.  If time permits in the 4.2.2 release, we should investigate the reason this change is required for our JScrib reports but not our BIRT reports.
Comment 1 Paul Slauenwhite CLA 2006-12-21 12:55:18 EST
Created attachment 56066 [details]
JScrib_Report_Error.jpg
Comment 2 Jerome Gout CLA 2007-01-11 03:28:19 EST
Paul, could you please provide the sequence to reproduce this problem.
Thanks
Comment 3 Jerome Gout CLA 2007-01-15 10:27:49 EST
defering as decided in today TPTP test meeting.
Comment 4 Paul Slauenwhite CLA 2007-01-16 09:28:05 EST
(In reply to comment #2)
> Paul, could you please provide the sequence to reproduce this problem.
> Thanks

1) Create a test suite.
2) Run the test suite and create an execution history.
3) Generate a JScrib report from the test suite.
4) Note the dialog informing the user that the color scheme has been changed to Windows Vista Basic temporarily by the Eclipse javaw.exe process (see the PID).

Note: You will need Windows Vista Aero installed with the necessary graphics/display capabilities. 
Comment 5 Valentina Popescu CLA 2007-03-14 13:52:39 EDT
4.4 is not a valid target
If this is planned to be done in 4.4 it should be assigned to an iteration, if not please reset target to future
Comment 6 Paul Slauenwhite CLA 2007-05-04 11:30:37 EDT
This defect is not blocking 163254 since it is a usability issue (no function is blocked).  We can still declare Vista support with this defect.
Comment 7 Paul Slauenwhite CLA 2007-05-18 16:18:37 EDT
This defect is a candidate for deferral from the 4.4 release.  If the originator has opposition, please provide an argument against this deferral.
Comment 8 Paul Slauenwhite CLA 2007-05-28 15:09:26 EDT
Assigning to i4 since i3 is complete but this defect belongs to a block of in-plan 4.4 defects that are candidates for deferral.
Comment 9 Joe Toomey CLA 2007-06-18 10:35:14 EDT
Approved for deferral from 4.4 by PMC.  Retarget to 4.5.
Comment 10 Paul Slauenwhite CLA 2008-03-31 12:14:19 EDT
Deferring to I7 as discussed by PMC/AG (http://wiki.eclipse.org/TPTP-AG-20080331#Test_Project).
Comment 11 Paul Slauenwhite CLA 2008-03-31 12:15:08 EDT
Deferring to future as discussed by PMC/AG (http://wiki.eclipse.org/TPTP-AG-20080331#Test_Project).
Comment 12 Paul Slauenwhite CLA 2009-06-30 07:00:30 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Comment 13 Paul Slauenwhite CLA 2009-07-03 06:53:12 EDT
Closing.