| Summary: | Error opening "New Report..." wizard (Right-click monitor > New Report...) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Mike Reid <mikereid> | ||||||||
| Component: | TPTP | Assignee: | Mike Reid <mikereid> | ||||||||
| Status: | CLOSED FIXED | QA Contact: | Kathy Chan <kathy> | ||||||||
| Severity: | major | ||||||||||
| Priority: | P2 | CC: | ernest, jcayne, jgwest | ||||||||
| Version: | unspecified | Flags: | jgwest:
pmc_approved?
(oec) ernest: pmc_approved+ jgwest: pmc_approved? (kathy) jgwest: pmc_approved? (paulslau) jgwest: pmc_approved? (jgwest) jcayne: review+ |
||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows XP | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Mike Reid
Created attachment 170891 [details]
Screenshot showing the error
Created attachment 170892 [details]
Workspace .log
Mike, Is this a regression? It looks like it might be a problem with one of the TPTP prereq. Please try to isolate the problem a bit further. Thanks! Created attachment 171017 [details]
Switch backslashes to forward slashes in plugin.xml
Seems that some underlying Eclipse API now no longer likes backslashes in URLs. Patch attached which specifies the path to the icon with forward slashes.
Patch confirmed on Linux and Windows. Joel can you please review this? Patch looks good. Please update the Copyright in the header. After searching, there do not appear to be other plug-ins using the extension point with backslashes in the URL. +1 for getting this in TPTP 4.7. Mike, please fill in the PMC template and ask Jonathan to bring this forward. Thanks! Jonathan, please bring this forward for PMC review: 1. Explain why you believe this is a stop-ship defect. How does the defect manifest itself, and how will users of TPTP / consuming products be affected if the defect is not fixed? Error message when opening "New Report..." wizard. 2. Is there a work-around? If so, why do you believe the work-around is insufficient? No workaround to prevent the error; dialog must be dismissed. 3. Is this a regression or API breakage? Explain. Regression; no API breakage. 4. Does this require new API? No 5. Who performed the code review? Joel Cayne 6. Is there a test case attached to the bugzilla record? No 7. What is the nature of the fix? What is the scope of the fix? What is the risk associated with this fix? The fix is a trivial, non-code fix. Scope limited to the "New Report..." wizard; risk is low. 8. Is this fix related to any standards that TPTP adheres to? If so, who has validated that the fix continues to adhere to the standard? No. Hi folks, requesting PMC approval for TPTP 4.7. Patch checked into HEAD w/ PMC approval. Verified fix in 4.7 release. Closing. |