Difference between revisions of "Developer Guide"
From OpenKM Documentation
| Line 26: | Line 26: | ||
* [[Debugging with GWT]] | * [[Debugging with GWT]] | ||
* [[Profiling OpenKM]] | * [[Profiling OpenKM]] | ||
| − | * [http://doxygen.openkm.com/ | + | * [http://doxygen.openkm.com/ Doxygen OpenKM 6.2.x] ( OpenKM packages & classes & files documentation ) |
| − | * | + | * Doxygen OpenKM 5.1.x ( Deprecated not available ) |
| − | * | + | * Doxygen OpenKM 5.0.x ( Deprecated not available) |
'''Note''': You can configure Eclipse to integrate with MantisBT. Read [http://sourceforge.net/apps/mediawiki/mylyn-mantis/index.php?title=Main_Page Mylyn-Mantis Repository Connector] for more info. | '''Note''': You can configure Eclipse to integrate with MantisBT. Read [http://sourceforge.net/apps/mediawiki/mylyn-mantis/index.php?title=Main_Page Mylyn-Mantis Repository Connector] for more info. | ||
Revision as of 14:46, 5 August 2013
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.
 |
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:
- Maven at http://maven.apache.org/
- Eclipse Juno (Eclipse IDE for Java EE Developers) at http://eclipse.org/juno/
- Subversion eclipse plugin at http://subclipse.tigris.org
- Maven to eclipse plugin at http://m2eclipse.sonatype.org
- Java JDK 1.6 at http://www.oracle.com/technetwork/java/javase/downloads/index.html
|
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. See Eclipse Indigo - Maven and Svn. |
 |
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.
- Configure Java in Eclipse
- Configure Tomcat server in Eclipse
- Maven installation
- Checkout source from Subversion
- Development tips
- Debug with Tomcat
- Debugging remote Tomcat server
- Debugging with GWT
- Profiling OpenKM
- Doxygen OpenKM 6.2.x ( OpenKM packages & classes & files documentation )
- Doxygen OpenKM 5.1.x ( Deprecated not available )
- Doxygen OpenKM 5.0.x ( Deprecated not available)
Note: You can configure Eclipse to integrate with MantisBT. Read Mylyn-Mantis Repository Connector for more info.
Eclipse Development Quick Install Guide
This quick install is valid for Eclipse Indigo.
- Download Eclipse IDE for Java EE Developers from http://www.eclipse.org/downloads/.
- Go to Help > Eclipse Marketplace and install these plugins:
Alternative: Add repository
- Subclipse 1.6.x Update Site -> http://subclipse.tigris.org/update_1.6.x
- Maven Integration for Eclipse - http://m2eclipse.sonatype.org/sites/m2e/
- Maven Integration for Eclipse Extras - http://m2eclipse.sonatype.org/sites/m2e-extras/
Know problems
When you build application on windows you can get the error create process error 206 the filename or extension is too long this is caused to a Windows OS limitation. To solve it is needed move .m2 repository to c:\ then go to Eclipse > Windows/Preferences/Maven/User Settings -> Create your own setting.xml with this content:
<settings>
<localRepository>c:/.m2/repository</localRepository>
</settings>
Deprecated
OpenKM version 5.x and older
- Configure JBoss server in Eclipse
- Debugging remote JBoss server
- Browsing embeded database
- Debugging OpenKM with JBoss
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.
