JOSM-latest & OpenStreetBugs - NullPointerException

[anonymous]

Looks like OSB plugin collides with the changed translation engine of JOSM. While starting JOSM with activated OSB plugin the following exception is thrown:

org.openstreetmap.josm.plugins.PluginException: Ein Fehler ist in dem Plugin osb aufgetreten.
	at org.openstreetmap.josm.plugins.PluginInformation.load(PluginInformation.java:127)
	at org.openstreetmap.josm.Main.loadPlugins(Main.java:275)
	at org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:208)
Caused by: java.lang.NullPointerException
	at java.util.Properties$LineReader.readLine(Properties.java:418)
	at java.util.Properties.load0(Properties.java:337)
	at java.util.Properties.load(Properties.java:325)
	at java.util.PropertyResourceBundle.<init>(PropertyResourceBundle.java:111)
	at org.openstreetmap.josm.plugins.osb.i18n.Messages.loadBundle(Messages.java:71)
	at org.openstreetmap.josm.plugins.osb.i18n.Messages.<init>(Messages.java:44)
	at org.openstreetmap.josm.plugins.osb.i18n.Messages.getBundle(Messages.java:58)
	at org.openstreetmap.josm.plugins.osb.i18n.Messages.translate(Messages.java:66)
	at org.openstreetmap.josm.plugins.osb.gui.OsbDialog.<init>(OsbDialog.java:83)
	at org.openstreetmap.josm.plugins.osb.OsbPlugin.<init>(OsbPlugin.java:77)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at java.lang.Class.newInstance0(Class.java:355)
	at java.lang.Class.newInstance(Class.java:308)
	at org.openstreetmap.josm.plugins.PluginInformation.load(PluginInformation.java:125)

[hampelratte]

Hi,

I can't reproduce this exception with josm-latest.jar and the latest plugin version 0.5.5. Could please update josm and the plugin and check, if it error still occurs?

[anonymous]

I can not reproduce it either using the latest JOSM from SVN. Therefore I assume this bug was caused by a bug in JOSM at this bug has already been solved.