-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 22.08.2010 10:31, schrieb Dirk Stöcker:
> If you can automate it, it may work. Hello Dirk, this is impossible. I cannot automatically detect if there are incompatible changes in remotecontrol. > Otherwise you will find, that > updating the version tends to be forgotten more often than it is updated. You are right. If I go this way I can only add a comment that updating the API version is important, but I cannot make sure that I or future developers will never forget to update it. > This is one of the reasons why josm has no upwards-compatibility for > plugins. The only possible thing would be to automatically update the API version on every change. But in this case it does not provide any advantage over using the SVN revision. I think I will keep it simple: WMSPlugin will not only check for a minimum SVN revision of remotecontrol but also for a maximum revision. Whenever remotecontrol gets recompiled with a new SVN revision, wmsplugin has to be updated. I will replace console messages with a normal message window to inform the user about this incompatibility. What do you think about this solution? Bodo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkxw6b0ACgkQnMz9fgzDSqd1ZwCfUwqmgzmnQ81VJJ3S/WWyVnvC OB4AoJDkeFzL3F2keYt8fxevTm6WvqJX =sk0b -----END PGP SIGNATURE----- _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
