Re: Versioning, workspaces and clone/merge functionality

[David Buchmann <da...@liip.ch>]

we also have open questions about this topic.

from what i did hear:

you start with the clone, then you can update/merge. you can only do
that on node, not single property, but the merge is done per property if
your node is versionable. if the node is versionable, a clone in a
different workspace also shares the same version history.

if you have child nodes that are themselves versionable (should be
simpleVersionable but currently isn't) the merge should skip them
theoretically. but we never managed to produce this behaviour.

i do hope some jcr pro could provide some clear explanations so we know
how to use it correctly and if there are bugs in the behaviour or not.

cheers,david

Am 31.05.2013 19:38, schrieb Ivan Vasyliev:
> Hello,
>  
> I have some issue with merging versioned nodes between workspaces. I have
> use-case when there is 3 types of data "PRODUCTION", "QA" and "USER".
> Production version of data available for access via API for external usage
> QA version of data created by software for users/admins to review and merge
> (approve) into production
> And last type - when user wants to change QA version of data and then merge
> into production
>  
> The issue I have is that node properties/nodes is not merged via
> VersionManager.merge/Version.update/VersionManager.doneMerge.
> Few doubt I have on this:
> Am I doing something wrong?
> I cant find code which merges properties. Is this not supported?
> What needs to be done to merge properties/nodes properly?
>  
> Please advise,
> Thank you in advance
> 
> 
> 
> 
> 
> --
> View this message in context: http://jackrabbit.510166.n4.nabble.com/Versioning-workspaces-and-clone-merge-functionality-tp4658803.html
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
> 

-- 
Liip AG // Agile Web Development // T +41 26 422 25 11
CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch