When you copy a versionable node in jackrabbit, is its version history
reset? I mean the new node starts with a fresh version history?
In subversion the version history of the new node (after a copy or move)
starts with the version of the source node at the time of the copy. Thus
when you examined the version history of the copied node, you see the
versions in the new place plus the versions when it was in the old
place. I believe that's why it's not necessary to copy the whole version
history, it's shared by both nodes, up to the time of the copy, and the
fact that it was copied it's also recorded.
Carlos
David Nuescheler wrote:
hi thomas,
i think this is an interesting usecase that you mention.
clearly jcr does not expect such an operation, and i have to admit
in my experience (cms) it was never necessary to copy the version
history. also, since geoff clemm as the main driver of the versioning
portion of the jcr spec has never mentioned such a need, despite
his extensive background in config management, i wonder if
this has a deeper reason.
how would you achieve that in cvs or svn, i dont think there is a
straight forward way either.
any thoughts?
regards,
david
