Difference between revisions of "Development tips OpenKM 4.0"

Latest revision as of 10:45, 23 November 2011

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:

To create symbolic links in windows use juntion.exe http://technet.microsoft.com/en-us/sysinternals/bb896768

In case you're making strong changes in OpenKM UI (GWT) we recommend disabling pom compile directive

<plugin>
    <groupId>org.codehaus.mojo</groupId>
        <artifactId>gwt-maven-plugin</artifactId>
        <version>1.1</version>
        <configuration>
            <runTarget>es.git.openkm.frontend.Main/index.html</runTarget>
        </configuration>
        <executions>
          <execution>
            <goals>
               <!-- <goal>compile</goal> -->
              <!-- <goal>generateAsync</goal>  -->
              <goal>test</goal>
            </goals>
          </execution>
        </executions>
    </plugin>

Is possible to compile GWT modules individually by this way: $ mvn gwt:compile -Dgwt.module=com.openkm.backend.Main

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.

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