Modify

Opened 4 years ago

Closed 4 years ago

#3111 closed defect (fixed)

Josm fails to load photos

Reported by: markus.lindholm@… Owned by: anonymous
Priority: major Component: Plugin
Version: tested Keywords:
Cc:

Description (last modified by stoecker)

How to reproduce:

File -> Open images with AgPifoJ
Select some jpgs (doesn't matter if only one or several)
Doesn't matter if this is the first thing done after starting Josm or if done after loading a data layer and after some editing

Path: trunk
URL: http://josm.openstreetmap.de/svn/trunk
Repository Root: http://josm.openstreetmap.de/svn
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Revision: 1788
Node Kind: directory
Last Changed Author: stoecker
Last Changed Rev: 1788
Last Changed Date: 2009-07-14 18:20:56 +0200 (Tue, 14 Jul 2009)

Memory Usage: 109 MB / 729 MB (40 MB allocated, but free)
Java version: 1.6.0_14

Plugins: AgPifoJutilspluginvalidatorwmsplugin
Plugin AgPifoJ Version: 16315
Plugin utilsplugin Version: 16290
Plugin validator Version: 16439
Plugin wmsplugin Version: 16442

java.lang.RuntimeException: java.lang.NoSuchFieldError: progressMonitor

at org.openstreetmap.josm.gui.PleaseWaitRunnable$3.run(PleaseWaitRunnable.java:120)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

Caused by: java.lang.NoSuchFieldError: progressMonitor

at org.openstreetmap.josm.plugins.agpifoj.AgpifojLayer$Loader.realRun(AgpifojLayer.java:113)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:95)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:144)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Attachments (0)

Change History (4)

comment:1 Changed 4 years ago by stoecker

  • Description modified (diff)
  • Owner changed from team to markus.lindholm@…
  • Status changed from new to needinfo

Try updating plugins (and/or delete agpifoj.jat from you plugins dir first). Something is mixed here. Your list states that you have agpifoj version 16315 (which would be correct for you josm version), but the error indicates you have a newer version, which is not correct.

comment:2 Changed 4 years ago by anonymous

  • Owner changed from markus.lindholm@… to anonymous
  • Status changed from needinfo to assigned

I tried the following

  • wipped out ~/.josm
  • redownloaded josm-tested.jar
  • installed just the AgPifoJ plugin
  • restarted
  • tried to load just one photo
  • it failed in the same manner

comment:3 Changed 4 years ago by jttt

It looks like I forgot to do two things when I fixed AgPiFoj to work with new JOSM: commit changes to svn before build and change Plugin-MainVersion.

I will have a look at ant whether it's possible to cancel build if there are local changes or plugin doesn't build against JOSM in Plugin-MainVersion

comment:4 Changed 4 years ago by stoecker

  • Resolution set to fixed
  • Status changed from assigned to closed

I fixed the entries. Please delete agpifoj.jar again and redownload. That should fix the issue.

Hopefully not to many people did update agpifoj already as the unchanged version number makes this really nasty.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.