Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 64.233.184.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=AU6effjxUaPOIALkFgIyeprjfv4ocjOKZ6hdKCjsGOcV0b63c8wRxDQ2EjXY2I1jCZ
         vR6LLFlqAgyN7splberh+sBhan9ZncIywvlSg1PTGv7PvVm66j8tOGZmRV7A6fNUGocZ
         +MbfOJ7bj1jt2nmKgLjvNSBWtHw5tUnKpChBs=
Message-ID: <510143ac0806200236j4af6a8e1l69d25ccfc415520@mail.gmail.com>
Date: Fri, 20 Jun 2008 12:36:46 +0300
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: Jackrabbit version numbers/names
In-Reply-To: <9912fc510806190705n45830a11x8ef6b9cd88489c9d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9912fc510806181738x17a1440cj1848bbc06d022d09@mail.gmail.com>
	 <510143ac0806190211k1e36b277l5d8131a0bccdc9ad@mail.gmail.com>
	 <c3ac3bad0806190255n30b38e9s1f0a9d0c96e66d66@mail.gmail.com>
	 <510143ac0806190435j2c30542bsa524a0e95b846ce@mail.gmail.com>
	 <9912fc510806190705n45830a11x8ef6b9cd88489c9d@mail.gmail.com>

Hi,

On Thu, Jun 19, 2008 at 5:05 PM, Pulla Venkat <pcsri1956@gmail.com> wrote:
> I can't reproduce example graph.. Can any body add snippet of code to
> reproduce the example below. Thanks

I added a test case that illustrates this:

http://svn.eu.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-core/src/test/java/org/apache/jackrabbit/core/integration/VersioningTest.java

> I am confused about how to go from versionname 1.0 to 2.0.

That's a bit tricky, as you need a checked out node with
jcr:rootVersion as the base version but you can't restore() a node to
the root version. One way (as you can see in the test case) to come up
with version 2.0 is to clone the versionable node to a separate
workspace before checking in the first version. I guess it could also
be possible to achieve the same using XML import, but I haven't tried
that.

Note that the above is not something that you'd typically do, but the
versioning code in Jackrabbit needs to be able to cover that case, and
the x.0 versions are used to cover that.

Note also that the exact version numbering mechanism is an
implementation-specific detail and the algorithm may even be modified
in future Jackrabbit versions, so you shouldn't rely on it too much in
client code. A client should treat the version names as opaque
strings. If you want more user-friendly version names, consider using
version labels or a specific property in the versionable node.

BR,

Jukka Zitting