ok, i figured out a way to start a new history on each import: i just remove the uuid property from the node in the xml file. that makes it a new node on each import. on the document view, the uuid was not exported, so the node was automatically a new one each time. now my tests run fine :-)
cheers,david ps: would have been nice if jcr:system was also importable, it would allow to migrate the full repository without using implementation specific means... Am 20.05.2011 11:24, schrieb David Buchmann: >>> you can't import jcr:system content using the JCR api. the /jcr:system >>> subtree >>> can be compared with the system tables in a rdbms. it contains in-content >>> representations of repository meta-data etc. > > ah, ok, thanks for the clarification. > > is there a way to get rid of the version history when importing? > > when i import the document view, the version history is reset. if i > import the system view, the history seems to stay there, adding new > versions on each test run... > > testing things that use versions of nodes, this is pretty confusing. > > cheers,david -- Liip AG // Agile Web Development // T +41 26 422 25 11 CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch
