On 2.9.14 2:38 , Michael Dürig wrote:
No need, I could reproduce this on trunk. Will follow up with an issue.
I think we need to change something here as the same name siblings
created through the upgrade tool are really unusable.
I spawned a thread on oak-dev for working out possible approaches:
http://markmail.org/message/7qczhkpicvq7q5ea
Michael
Michael
On 2.9.14 2:20 , Torgeir Veimo wrote:
Correct. This was with oak-run built from 1.0.3 if I remember
correctly. I can try again with 1.0.5.
On 02/09/2014, Michael Dürig <[email protected]> wrote:
On 2.9.14 2:05 , Torgeir Veimo wrote:
I did actually convert the content using oak-run. We don't actually
need SNS support, we only need to migrate existing content, and it
would be preferable if oak-run uses a pattern for renaming them that
allows later editing of said nodes.
IIUC you used oak-run to migrate an existing repo containing SNSs and
ended up with a Oak repo where these nodes are named like[1] this[2].
Now you can't rename these nodes as this throws a RepositoryException!?
Michael
