[josm-dev] Update Plugins fails

[Dirk Stöcker]

On Mon, 18 Aug 2008, Frederik Ramm wrote:

> Other plugins are again one step more complex. They use the SVN revision
> number as their version and thus make manual intervention unnecessary.
> There is a catch, however, at least with subversion under Linux. If you
> make a change to the plugin, then commit ("commited revision #1234"),
> then build - your plugin will still be built with the OLD revision
> number! You change the wiki table to mention version #1234, and wo-hoo,
> round the user goes in download circles because your plugin still says
> it is #1111 (or whatever) although having been built from revision 1234
> sources! Why is that? It seems that the revision indicator used by the
> build process is not updated when checking in, only when checking out.
> So after changing your plugin, do "svn commit" (note down version number
> reported!), followed by "svn update", and only THEN do "ant" do build
> the .jar; then do "cd ../../dist" and "svn commit myplugin.jar", and
> then change the wiki page to the version number reported when you
> commited your source changes.

I added a getversions script in dist directory for that purpose. So when 
checking in a new plugin, call this, check if all the SVN and time is 
correct, then commit the jar and then update wiki page according to what 
the getversions script call said :-).

Ciao
-- 
http://www.dstoecker.eu/ (PGP key available)