[josm-dev] "unmaintained" plugins

[MP]

>  > Before someone deleted it from the plugins page (so it WAS available
>  > through "official JOSM plugin update system" and it was pointing to
>  > corrent URL with newest and working version) it was maintained and
>  > perfectly working. I wonder how someone have discovered that is is
>  > unmaintained?
>
> Because we got lots of bugreports which showed that the plugin was not
>  actively developed for a long time now.

Which bugreports?
I found Ticket #3554, but it seems that reporter had old version of
plugin (I'm not sure whether I bumped version of the plugin in
manifest, so perhaps that could be partly my fault too), since the
issue is reported on 20th of september and that bug I fixed 11th
september (and I uploaded the fixed version to usual site at git.wz.cz
and I used that exact .jar myself till now)
I didn't knew about that bug before now ....
That version worked for me till now - I often upgrade to newest JOSM
and I relatively often use the plugin, so I would notice any breakage
quite soon.

I asked for SVN write access in OSM repository, so once/if I get that,
I'll continue development in SVN (.../editors/josm/plugins/)

I've also registered in trac under username "bilbo", so if there is
some mechanism to automatically assign bugs in multipolygon plugin to
me, then you can activate it :)

> I introduced this check to get rid of plugins which are no longer working.
>  Most users aren't able to decide, so JOSM needs to do this for him. And a
>  lot of users install ALL plugins without thinking if they need them or
>  not.

Perhaps that check should also check for plugin version - if you know
that plugin is unmaintained and version X (the last that is out) is
not working, then you can limit that check to version <=X and assume
that if someone will release version higher than X, then it is
something newer than last known broken version and it will be probably
fixed. So no more warning is required. Especially since this warning
can push someone to fix the problem and publish new fixed version :)
I published new version of multipoly with the version bumped, so that
should "force" people to upgrade

Martin