1
votes

We are working on a migration tool for moving data from an older version to a newer version of a custom system that is based on a JCR implementation (either Jackrabbit or Modeshape). Our problem is related to JCR versioning support for some type of custom nodes. Migration requires adding new properties to that custom nodes and implicitly to all versions of that node therefore requiring adding new properties to frozen nodes. As frozen nodes are read-only, is there a workaround that would allow changing their content?

Thanks in advance.

1

1 Answers

0
votes

I don't know of a way in either ModeShape or Jackrabbit to modify the version history without explicitly checking out those older versions and then checking them back it. But that will essentially branch the version history at all checked-in versions. That's probably not very attractive.