#5959 closed defect (duplicate)
IncompatibleClassChangeError when starting JOSM rev:3902
Reported by: | jBeata | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
The following error occurs when starting JOSM rev.3902:
Build-Date: 2011-02-15 09:57:27
Revision: 3902
Is-Local-Build: true
Identification: JOSM/1.5 (3902 SVN en)
Memory Usage: 15 MB / 247 MB (12 MB allocated, but free)
Java version: 1.6.0_23, Sun Microsystems Inc., Java HotSpot(TM) Client VM
Operating system: Windows 7
java.lang.IncompatibleClassChangeError: Expecting non-static method org.openstreetmap.josm.actions.DownloadReferrersAction.getCurrentDataSet()Lorg/openstreetmap/josm/data/osm/DataSet;
at org.openstreetmap.josm.actions.DownloadReferrersAction.updateEnabledState(DownloadReferrersAction.java:93)
at org.openstreetmap.josm.actions.JosmAction.initEnabledState(JosmAction.java:160)
at org.openstreetmap.josm.actions.JosmAction.installAdapters(JosmAction.java:149)
at org.openstreetmap.josm.actions.JosmAction.<init>(JosmAction.java:93)
at org.openstreetmap.josm.actions.JosmAction.<init>(JosmAction.java:68)
at org.openstreetmap.josm.actions.DownloadReferrersAction.<init>(DownloadReferrersAction.java:29)
at org.openstreetmap.josm.gui.MainMenu.<init>(MainMenu.java:113)
at org.openstreetmap.josm.Main.<init>(Main.java:215)
at org.openstreetmap.josm.gui.MainApplication.<init>(MainApplication.java:58)
at org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:225)
Attachments (0)
Change History (6)
comment:1 by , 14 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
follow-up: 3 comment:2 by , 14 years ago
comment:3 by , 14 years ago
follow-up: 5 comment:4 by , 14 years ago
The issue is caused by the change of getCurrentDataSet() in JosmAction, which now got static. Java dependency checking is broken and does not catch such issues properly - thus the ant clean. If you have the problem after ant clean, then somehow the clean does not work reliable or you start the wrong jar. Try following steps:
- ant clean
- svn status --no-ignore --> see what generated files are left --> delete them
- start josm --> must fail, as unbuild
- ant
- start josm
Be sure this is not caused by an not-yet-updated plugin
comment:5 by , 14 years ago
Replying to stoecker:
The issue is caused by the change of getCurrentDataSet() in JosmAction, which now got static. Java dependency checking is broken and does not catch such issues properly - thus the ant clean. If you have the problem after ant clean, then somehow the clean does not work reliable or you start the wrong jar. Try following steps:
- ant clean
- svn status --no-ignore --> see what generated files are left --> delete them
- start josm --> must fail, as unbuild
- ant
- start josm
Be sure this is not caused by an not-yet-updated plugin
Thanks for the reply. I did update again JOSM from svn, and delete manually the files from dist and rebuild again with ant. Now JOSM works without this problem.
Closed as duplicate of #5904.