Difference between revisions of "Development tips"

From OpenKM Documentation
Jump to: navigation, search
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
We recommend downloading JBoss+OpenKM from SourceForge, remove ''OpenKM.war'' and develop with this JBoss server configuration. For better development we recommend not deploying ''OpenKM.war'' file it's better setting in ''$JBOSS_HOME/server/default/deploy'' some alias to ''target/OpenKM'' folder:
* [[Development tips OpenKM 6.0]]
* [[Development tips OpenKM 5.1]]
* [[Development tips OpenKM 5.0]]
* [[Development tips OpenKM 4.0]] ( covers 4.1 too )
In case you're making strong changes in OpenKM UI (GWT) we recommend disabling pom compile directive
<source lang="xml">
              <!-- <goal>compile</goal> -->
              <!-- <goal>generateAsync</goal>  -->
{{Advice|Is possible to compile GWT modules individually by this way:
<nowiki>$ mvn gwt:compile -Dgwt.module=com.openkm.backend.Main</nowiki>
You might be interested in running frontend and backend GWT packaging from eclipse. Go to run configurations and add in maven build
To achieve a faster compile we use to development Firefox, uncommenting gecko line on file Main.gwt.xml GWT compilation only for gecko browser runs fine. Don't forget at finish to comment it and try application with IE or other browsers. Now are two files called Main.gwt.xml one for frontend and other to backend.
<source lang="xml">
<!-- Compile for Firefox only -->
<set-property name="user.agent" value="gecko"/>
[[Category: Developer Guide]]
[[Category: Developer Guide]]

Latest revision as of 16:14, 24 October 2012