|
From: Julien C. <jul...@gm...> - 2009-04-16 10:47:04
|
svn info gives a revision number which is not up to date if you haven't done previously an update (at least in eclipse). On Thu, Apr 16, 2009 at 11:45 AM, Viliam Holub <vil...@uc...> wrote: > > Hi all, > > so I'll be probably the first one who will omit this ;) > > Isn't there an easier way? I.e. what if the revision number would be > automatically the svn revision number? I'm not an expert in svn hooks > though. > > Viliam > > On 16. Apr (Thursday) v 11:23:15 +0100 2009, Julien Charles wrote: > > Hi all, > > I have added the revision numbering to the version number because it is > > quite useful when you are testing the program. > > Actually there is some kind of bug (maybe a feature...?) that arises when > > doing that is that a commit doesn't change your local version > > of the repository, while changes the remote version, at least this > happens > > with subclipse. > > So be sure to _update_ after any commit otherwise you will get bad > version > > number. > > > > Julien > > > > ------------------------------------------------------------------------------ > > Stay on top of everything new and different, both inside and > > around Java (TM) technology - register by April 22, and save > > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > > 300 plus technical and hands-on sessions. Register today. > > Use priority code J9JMT32. http://p.sf.net/sfu/p > > > _______________________________________________ > > Clops-users mailing list > > Clo...@li... > > https://lists.sourceforge.net/lists/listinfo/clops-users > > > -- > Viliam > |