| Summary: | [Compatibility] 'forcePluginActivation' attribute not honoured for property testers | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Paul Webster <pwebster> | ||||||
| Component: | UI | Assignee: | Paul Webster <pwebster> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P3 | CC: | ob1.eclipse, remy.suen | ||||||
| Version: | 4.1 | ||||||||
| Target Milestone: | 4.2 M1 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 200395 [details]
store the boolean in the context
Remy, what about this?
PW
Grumble, my patch includes way to many changes. PW Created attachment 200396 [details]
store the boolean in the context v02
The patch is worse, but at least it is accurate.
PW
(In reply to comment #3) > Created attachment 200396 [details] > store the boolean in the context v02 > > The patch is worse, but at least it is accurate. It still has a lot of other changes. Or are you aware of that? (In reply to comment #4) > > It still has a lot of other changes. Or are you aware of that? No, those are the changes. PW (In reply to comment #5) > > It still has a lot of other changes. Or are you aware of that? > > No, those are the changes. Forget that. I was clicking on the wrong attachment. (In reply to comment #3) > Created attachment 200396 [details] > store the boolean in the context v02 Confirmed on my end that this patch allows property testers to force the activation of its parent bundle. |
It seems like we don't honour the allowPluginActivation/forcePluginActivation any more. <visibleWhen checkEnabled="false"> <iterate operator="or"> <or> <test forcePluginActivation="true" property="z.ex.rcp.mail.propertyTester1.test"> </test> <test forcePluginActivation="true" property="z.ex.rcp.mail.propertyTester2.test"> </test> </or></iterate> </visibleWhen> PW