#19973 closed enhancement (fixed)
Tag2Link: update to 2020.10.18
Reported by: | simon04 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 20.11 |
Component: | Core tag2link | Version: | |
Keywords: | Cc: |
Description
Attachments (0)
Change History (5)
comment:1 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 4 years ago
Not sure if this was the cause, but it is probably related. I see this error when I start JOSM from Eclipse:
2020-10-25 09:17:00.360 SEVERE: Failed to initialize tag2link rules 2020-10-25 09:17:00.390 SEVERE: java.io.IOException: Failed to open input stream for resource 'resource://META-INF/resources/webjars/tag2link/2020.10.18/index.json' java.io.IOException: Failed to open input stream for resource 'resource://META-INF/resources/webjars/tag2link/2020.10.18/index.json' at org.openstreetmap.josm.io.CachedFile.lambda$0(CachedFile.java:231) at java.util.Optional.orElseThrow(Optional.java:290) at org.openstreetmap.josm.io.CachedFile.getInputStream(CachedFile.java:231) at org.openstreetmap.josm.tools.Tag2Link.initializeFromResources(Tag2Link.java:111) at org.openstreetmap.josm.tools.Tag2Link.initialize(Tag2Link.java:95) at org.openstreetmap.josm.spi.lifecycle.InitializationTask.call(InitializationTask.java:33) at org.openstreetmap.josm.spi.lifecycle.InitializationTask.call(InitializationTask.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
I don't see it when I start JOSM from the command line when I build it with ant clean dist, so I assume that the build process does something that changes or adds ressources which do not exist for Eclipse.
comment:4 by , 4 years ago
Seems I did not. Problem solved now. Thanks!
A refresh (F5) of the project isn't enough. This is all quite confusing. I am still on Eclipse Version: Neon.3 Release (4.6.3). After an svn update on the command line parts of the project are auto-updated by the svn plugin, but ivy somehow needs a manual refresh.
In 17246/josm: