Callbacks happen in the AWT-AppKit thread

Issue #2 resolved
Emilian Bold
repo owner created an issue

Which means the listener must stay as little as possible in AWT-AppKit (ie. call EventQueue).

{{{
"AWT-AppKit" daemon prio=5 tid=1030f3800 nid=0x7fff70c2cca0 in Object.wait() [7fff5fbf9000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method) - waiting on <10db3b7f8> (a java.awt.EventQueue$1AWTInvocationLock)
at java.lang.Object.wait(Object.java:485)
at java.awt.EventQueue.invokeAndWait(EventQueue.java:1029) - locked <10db3b7f8> (a java.awt.EventQueue$1AWTInvocationLock)
at org.openide.util.Mutex.doEventAccess(Mutex.java:1391)
at org.openide.util.Mutex.readAccess(Mutex.java:271)
at org.netbeans.core.windows.services.DialogDisplayerImpl.createDialog(DialogDisplayerImpl.java:110)
at org.netbeans.modules.autoupdate.ui.wizards.InstallUnitWizard.implInvokeWizard(InstallUnitWizard.java:92)
at org.netbeans.modules.autoupdate.ui.wizards.InstallUnitWizard.invokeLazyWizard(InstallUnitWizard.java:82)
at org.netbeans.modules.autoupdate.ui.actions.AutoupdateCheckScheduler$8.actionPerformed(AutoupdateCheckScheduler.java:500)
at ro.emilianbold.notifications.GrowlNotification$1.notificationWasClicked(Unknown Source)
at info.growl.GrowlNative.fireCallbacks(GrowlNative.java:71)

Locked ownable synchronizers: - None
}}}