Developer Guide

From OpenKM Documentation
Revision as of 13:34, 21 November 2012 by Jllort (talk | contribs)

Jump to: navigation, search

The developer environment can be set in any Operating System (Linux, Windows, etc.) since it is a multi-platform system, but Linux is recommended, because is what it is being used.


Nota clasica.png Youtube - How to install OpenKM developement guide video

You need to install Maven, eclipse IDE and some plugins. For OpenKM 4.0 and 5.0 you have these requirements:


Nota clasica.png Starting from Eclipse Galileo you have a Marketplace accessible from Help > Eclipse Marketplace... Here you can search for "maven" to install the "Maven Integration for Eclipse" and "Maven Integration for Eclipse (Extras)" solutions. Also you can search for "subversion" to find the "Subclipse" plugin.


Nota idea.png The easier way to get an Eclipse installation with the required plugins is using JBoss Developer Studio.

Once all them are installed, you can download OpenKM and build it.

Note: You can configure Eclipse to integrate with MantisBT. Read Mylyn-Mantis Repository Connectofor more info.

Eclipse Development Quick Install Guide

This quick install is valid for Eclipse Indigo.

  1. Download Eclipse IDE for Java EE Developers from http://www.eclipse.org/downloads/.
  2. Go to Help > Eclipse Marketplace and install these plugins:
    1. Maven Integration for Eclipse
    2. Subclipse

Alternative: Add repository

Deprecated

OpenKM version 5.x and older

Changelog

Changes between developer guide 5.0 to 6.0

  • GWT 2.4.0
  • OpenKM now is executed under tomcat
  • Changed to Eclipse Juno

Changes between developer guide 4.0 to 5.0

  • Development tips changes ( how to enable OpenKM extensions in compilation and disable automatic GWT compilation )
  • GWT 2.0.4
  • Java package has been refactoring to "com.openkm" all references to older package in configuration files has been changed

Changes between developer guide 2.0 to 4.0

  • Changed to Eclipse Galileo
  • Now we use maven in replacement of JBoss Tools

Changes between developer guide 1.2 to 2.0

  • Changed IDE to Eclipse Europa / JBoss tools, before was JBoss IDE.
  • GWT 1.5.3 is needed to compile, before was version 1.4.6
  • Changed packaging to new jboss tools packaging.
  • Changed GWT generating to temporary JBoss folder to project folders to developing.
  • Added new generateback.sh and generateback.bat to GWT admin.
  • Upgraded JBoss server to version 4.2.2.GA

Changes between developer guide 1.0 and 1.1 to 1.2

  • GWT 1.4.6 is needed to compile, before was version 1.3.3.
  • Changes on GWT shell configuration, now not uses GWTDS variable ( code deleted ).
  • Configured generate.sh to deploy to tmp JBoss with OpenKM.ear deployed to fast developing.
  • Added gecko to Main.gwt.xml to fast compiling only gecko when is uncommented.