On Fri, Apr 05, 2013 at 10:08:03PM +0200, Snjezana Peco wrote:
A test doesn't have to be an UI test to open the
UsageReportEnablementDialog dialog.
The dialog is created using the startup extension point. That's why the
usage plugin will always try to open this dialog.
The issue can't be reproduced on Windows. It can always be reproduced on
Linux when using Kepler M6. Not sure for Mac.
The issue isn't caused by changes in usage/JBT, but in Kepler M6.
hmm - what is that change ?
Is it affecting how startup extension points are run or how tests are run together ?
Seems like a subtle surprising change ...curious what it is and if it was intended to
happen.
Any idea ?
/max