[josm-dev] Refactoring of the JOSM architecture vs. Plugins

[Petr Nejedly]

Robin Rattay napsal(a):
> J.H. schrieb:
>> - Introduce an API version management for plugins (let a plugin return
>> its expected API version. Assume pre-version-management version on
>> NoSuchMethodError).
>> - Make it easy for refactorers to run a workspace with all the
>> (critical) plugins checked out.
>> - By the way of refactoring, clean up the code design, and create
>> well-defined APIs as we go along.
>> - Publish API change notes to give third-party plugin developers a
>> chance of keeping up.
> 
> It may be a dumb idea, but what about using a rich client platform like
> Eclipse or NetBeans? That way you get things like a plugin
> infrastructure built in.

Yes, at a cost. Is the benefit of the platform worth the cost?

Moreover, at least NetBeans expect that a plugin API evolve
in a sensible way, that is, every plugin designed for lower version
should work with higher version of given API. Of course, there is a possibility
to claim that your API changed incompatibly (changing so called major version
of the API providing module), but it is used very rarely in the NetBeans land
("preservation of investment").

Note: Of course I think NetBeans is a great platform. I just thing it is
still too big for the project of the JOSMs size.

-- 
Petr "Nenik" Nejedly, NetBeans/Sun Microsystems, http://www.netbeans.org
355/113 -- Not the famous irrational number PI, but an incredible simulation!