OpenKM trunk - deploment and repository compatibility

[spawn]

Hi,

just starting to join the OpenKM project development, I have some question I can't find answers to:

After compiling trunk version of OpenKM, there are numerous errors like, witch are caused (as I understand) by the incompatibility of the repository and the trunk version, also there is no README nor any information about the intended server back-end - I tried to test the OpenKM trunk version with the OpenKM4.0 version from sourceforge by replacing OpenKM.war? I have checked everywhere from wiki to forum no infos about trunk issues and setup guides or infos.

error: actual:11 nou:24
....
OKM-003017(GetRootNode): Session lost
Session lost
OKM-003017(GetRoot): Session lost
Session lost
OKM-003017(GetGrantedUsers): Session lost
Session lost

How to setup trunk version?
Can the trunk version be used with the environment from 4.0?
How to migrate repository from 4.0 to the trunk version?

[jllort]

No no no no

You must not downloading head trunk because there're serveral internal repository changes that we've still not yet done, and by fact is not compatible directly with version 4, it'll be necessary a migration process, like has been in other versions.

If you want to make some changes in actual version 4, you must download from here https://openkm.svn.sourceforge.net/svnr ... 4.0/openkm that's the version 4.0 branch

If you're planning to make some enhancement I suggest you contact with us. Probably if it's good enhancement we could add in OpenKM by default or we can make it pluggable ( if you have on mind some special integration that you want to comertialize, that's only a possible example ).

I want to remember that anybody collaborates with us in some way, like supporting documentation, developing, etc.. are always welcome and receibe from us free access to OpenKM Network. We've planned a weekly growing of the documentation, hope in several months could note the difference.

[pavila]

The development version of OpenKM are actually very unstable and may be necessary to recreate the repository sometimes. It is not intended to be used for anymore than the development team. If you want to test the bleeding-edge features, is better to contact us to be informed about the actual trunk code stability.