Open Source Document Management System | OpenKM

Hi

I download the OpenKM portable Dev and i updated to 6.3.3 from Git repo.

I have not worked with this system and I do not know what is the fastest way to compile.

Try with frontent screens to check the use, change values and use "Build openkm 6.3" with: clean gwt:compile compile war:exploded.

But waste several minutes to finish.

What is the best method to test without compiling the entire project? If it exists.

Thanks

What consumes a lot of core's and ram if GWT compilation for all the browsers. You can save a lot of time compiling only for firefox or chrome. Here is explained how doing it:
https://docs.openkm.com/kcenter/view/ok ... ermutation

If you are making only frontend changes, then I suggest do not compile the entire project for each change. In this scenario have two options:
1- Compile only GWT ( will take some time ) take a look here https://docs.openkm.com/kcenter/view/ok ... romeclipse
2- Enable remote debug ( super dev mode or GWT Shell ). Althought plugin for GWT shell is discontinued in new browsers, using older firefox you can take it running ( I think portable edition comes with portable firefox with this plugin into ). Take a look here https://docs.openkm.com/kcenter/view/ok ... rinterface

You can take a quick look at this documentation section https://docs.openkm.com/kcenter/view/ok ... pment.html

We are now working in release a new development environment based in virtual machine ( OVA ) what we think will be more confortable and portable rather existing zip.

I am testing with one permutation using this property in main.gwt.xml

<!-- Compile for Firefox only -->
<set-property name="user.agent" value="gecko_18"/>

From this help page : https://docs.openkm.com/kcenter/view/ok ... ermutation

I think this is an error, and the correct property is :

<!-- Compile for Firefox only -->
<set-property name="user.agent" value="gecko1_8"/>

Like GWT agent list say :

https://gwt.googlesource.com/gwt/+/mast ... nt.gwt.xml

Thanks

Thanks, I have corrected the mistake in the documentation.