[
https://issues.apache.org/jira/browse/PIVOT-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808634#comment-13808634
]
Sandro Martini commented on PIVOT-927:
--------------------------------------
Hi all,
the problem here seems strange ... I did some check and Pivot jars downloaded
from Maven Central Repository are that of 2.0.3 release (even because I
generate them with a script "near" to release generation scripts, and they are
built just after Release jars, from the same sources ) ... but I'll try to do
other tests.
For local sources, you can use our ant tasks to install generated maven jars in
your local maven Repository (under the user profile, in the folder .m2 , in the
subfolder repository/org/apache/pivot/).
You could even do a a manual cleanup, like rename/delete your local folder for
our jars, and force Maven to download another time to be sure they are right.
if useful, note that even when only "consuming" Maven jars, you can tell Maven
to download even sources and javadoc related jars (if any), for example the
Eclipse Maven plugin has this feature (since many time).
In this way you can inspect sources jars because they are in the same folder of
"normal" jars downloaded, and eclipse can link to them in your projects.
Note that in eclipse it's useful sometimes to force an update so eclipse
settings will be refreshed from pom.xml file.
Last, some time ago I wrote a minimal test project to test Pivot in a Maven
project from Java, you can find it here:
http://code.google.com/a/apache-extras.org/p/pivot-stuff/
the project is pivot-java-test-maven .
if you have some time, could you download it, and tell us if the same error
happens ?
And if yes, please could you attach here a minimal sample (inside a zip), so we
can look better at the error ?
Thanks a lot.
> Unexpected NPE
> --------------
>
> Key: PIVOT-927
> URL: https://issues.apache.org/jira/browse/PIVOT-927
> Project: Pivot
> Issue Type: Question
> Affects Versions: 2.0.3
> Reporter: Łukasz Hanusiak
> Assignee: Roger Whitcomb
> Fix For: 2.0.4, 2.1
>
>
> After upgrading to pivot 2.0.3 my application randomly becomes unresponsive
> after throwing NPE with following trace:
> java.lang.NullPointerException
> at
> org.apache.pivot.wtk.ApplicationContext$DisplayHost.processMouseMotionEvent(ApplicationContext.java:1132)
>
> at java.awt.Component.processEvent(Unknown Source)
> at
> org.apache.pivot.wtk.ApplicationContext$DisplayHost.processEvent(ApplicationContext.java:793)
>
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> After mentioned exception occurs user is unable to use any element of UI.
> Only application restart helps solve this problem. Even more confusing is
> fact that problem sometimes occurs after few minutes and sometimes after few
> hours or even days.
> Can anybody give me some pointers how to workaround / fix this situation?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
