#4354 closed defect (fixed)
JOSM forgets all plugins at every update
Reported by: | Ldp | Owned by: | Ldp |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
Every time I build a newer version of JOSM and start it, it forgets all plugins I had previously loaded.
JOSM 2832, but noticed this since at least 2830.
I have
message.pluginmanger.version=true message.pluginmanger.version.value=1
The plugins= line is missing from the preferences file, in this case.
PS: Notice typo: manger -> manager
Attachments (0)
Change History (5)
comment:1 by , 16 years ago
Owner: | changed from | to
---|
comment:2 by , 16 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
comment:3 by , 16 years ago
Those message.pluginmanager settings are because I have set "Do not ask" and "Update plugins" on startup.
I build with svn up ; ant clean dist and then use the resulting josm-custom.jar.
$ grep plugin preferences|grep -v "^wmsplugin"|grep -v "^cache"|grep -v mirror message.pluginmanager.version=false message.pluginmanager.version.value=1 pluginmanager.lastupdate=1263389298595 pluginmanager.version=2837 plugins=wmspluginremotecontrolvalidatorAddrInterpolationterracermultipoly
However, updating from 2837 to 2838, I could not reproduce this again. I'll reopen if it happens again.
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | needinfo → closed |
OK, I'm closing it in the meantime.
comment:5 by , 16 years ago
#4364 could be exactly what happened. I was editing the boundary colour at the same time (hate the orange, can hardly see when it's selected or not!).
Can't reproduce.
These are strange looking preferences:
To the best of my knowledge there are just two preferences for the pluginmanager:
Do you build from a local SVN checkout? Do you have a local installation task to install the local build?