| Summary: | [misc] FilterMessages is a copy of Messages - causing NLS warnings | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Ian Tewksbury <itewksbu> | ||||||||
| Component: | Debug | Assignee: | Nitin Dahyabhai <thatnitind> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | Michael Rennie <Michael_Rennie> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | cmjaun, karasiuk, thatnitind | ||||||||
| Version: | 3.2.4 | Flags: | thatnitind:
review+
karasiuk: review+ |
||||||||
| Target Milestone: | 3.2.5 | ||||||||||
| Hardware: | All | ||||||||||
| OS: | All | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Ian Tewksbury
Created attachment 196205 [details]
Fix patch
Patch that removes redundant FilterMessages class and updates the one reference to it to use existing Messages class.
(In reply to comment #1) Whoops, I just opened bugzilla 346661 for this problem and submitted a different patch :-) I think that the FilterMessages class is still needed in order to prevent some unwanted bundle activation cases. (In reply to comment #2) > (In reply to comment #1) > Whoops, I just opened bugzilla 346661 for this problem and submitted a > different patch :-) > > I think that the FilterMessages class is still needed in order to prevent some > unwanted bundle activation cases. You're right. (In reply to comment #3) > > You're right. This seems to be fallout from fix for bug 320407. I think the best solution to this would be to remove the filter - which no longer seems to be working anyway - and the offending messages file. Very well. We'll do that. Created attachment 197512 [details]
fix for HEAD
Here is a patch that removes the filter completely from HEAD
Created attachment 197513 [details]
fix for 3.2.5
here is the fix for 3.2.5
*** Bug 346661 has been marked as a duplicate of this bug. *** Nitin, Gary, please review the patches (In reply to comment #9) > Nitin, Gary, please review the patches Looks ok to me. Is this all ready to be checked in? (In reply to comment #11) > Is this all ready to be checked in? Yes. Checked into HEAD and 3.2.5. |