gmane.comp.apache.jackrabbit.user

Anil K. Kotha | 26 Aug 09:38

Regarding Versioning

Hi All,

      I have found the following description for versioning in
jackrabbit mail archives.

Here's the relevant documentation from

AbstractVersionManager.calculateCheckinVersionName:

The name is determined as follows:

* first the predecessor version with the shortes name is searched.

* if that predecessor version is the root version, the new version

gets the name "{number of successors}+1" + ".0"

* if that predecessor version has no successor, the last digit of it's

version number is incremented.

* if that predecessor version has successors but the incremented name

does not exist, that name is used.

* otherwise a ".0" is added to the name until a non conflicting name is
found.

Example Graph:

(Continue reading)

headers

Alexander Klimetschek | 26 Aug 13:31

Re: Regarding Versioning

On Tue, Aug 26, 2008 at 9:41 AM, Anil K. Kotha <Anilk <at> 2xprime.com> wrote:
> 1)    We are using jackrabbit to save pdf files, and the version format
> we use is 1.1,1.2,1.3...
>
> But in some rare cases I getting the version as 1.2.0,1.2.1,... like
> this..

AFAIK this happens when you restore the 1.2 version and add new
versions after it.

> 2)    What could be the reason for this and how can I restrict it?

You cannot "rely" on the version number scheme (or configure it) - it
is implementation-specific and not standardized. If you want your own
versions (eg. to display in the UI), you can use version labels.

Regards,
Alex

--

-- 
Alexander Klimetschek
alexander.klimetschek <at> day.com