Closed Bug 484137 Opened 12 years ago Closed 12 years ago

remove plugin tester and spy tools


(Core :: Plug-ins, defect)

Not set





(Reporter: jaas, Assigned: jaas)



(1 file, 1 obsolete file)

Attached patch fix v1.0 (obsolete) — Splinter Review
The plugin tester and spy tools in our tree are outdated, unmaintained, and not working as far as I know. We have no plans to revive them and if we wanted such tools we would almost certainly rebuild them from scratch using modern APIs. We should probably remove them from the tree.
Attachment #368192 - Flags: superreview?(jst)
Attached patch fix v1.1Splinter Review
includes makefile fixes
Attachment #368192 - Attachment is obsolete: true
Attachment #368301 - Flags: superreview?(jst)
Attachment #368192 - Flags: superreview?(jst)
Comment on attachment 368301 [details] [diff] [review]
fix v1.1

Yeah, let's get rid of these...
Attachment #368301 - Flags: superreview?(jst)
Attachment #368301 - Flags: superreview+
Attachment #368301 - Flags: review+
pushed to mozilla-central
Closed: 12 years ago
Resolution: --- → FIXED
Josh, are you going to remove these files on the 1.9.1 branch as well?
I wasn't planning on it, why?
We are still building in 1.9.1 this code on OS/2 when we enable tests. On trunk after the removal I switched over to use the new test plugin (at least the same skeleton file as gtk2)(bug485073). I think it would be better for OS/2 to switch on 1.9.1 branch as well to build the new test plugin. This switch would include the changes you did in the top Makefile with regard to OS/2.
Thus, I wanted to know, whether its better to wait a bit until the patch here goes to 1.9.1. But as you said it's not planned for 1.9.1, I'll append the Makefile changes to bug485073. Thanks
You need to log in before you can comment on or make changes to this bug.